In README: What's New ---------- The following features have been added or improved since the second generation of this product * Two versions of the server are included in this release: a single process server similar to the mSQL 2.x server called msql3d, and a new multi-process server called msql3_broker. The broker based server can handle multiple queries simultaneously by spreading the queries over a farm of backend procsses. However, there is a performance overhead involved so the single procss server should be used unless you specifically require the extra functionality of the broker based server. * Several new data types are supported in this release. Integers of 8 bits, 16 bits, 32 bits and 64 bits are supported using the int8, int16, int32 and int64 data types. Native support for Internet Protocol addresses (IP Version 4 addresses) is also included using the ipv4 type. * Support for value functions (not aggregate functions) has been included. String functions available in this release include UPPER, LOWER, LENGTH, SUBSTR, TRANSLATE, REPLACE and SOUNDEX. Numeric functions included are ABS, CEIL, FLOOR, MOD, SIGN, and POWER * Support for result tables is now available using the SELECT INTO construct. A query such as "SELECT * INTO young FROM staff WHERE age < 30" would create a new table called 'young' countaining the results of the specified query. Please remember that the result tables are not transient tables. They must be DROPed if you want to remove them. * Index range support has been included, as has support for the BETWEEN operator. Queries that use range based conditions, such as < <= > >= and BETWEEN, on an indexed field will now see a significant increase in performance. * The code has been modularised to greatly reduce the internal complexity of the code. Each module has been reviewed with respect to efficiency and reliability. The servers are now smaller, faster, and more resilient than the 2.x servers. In fact, in normal benchmark testing, the single process server is more than twice as fast as the last of the 2.0.x release servers. How-To-Repeat: N/A
What's the reasons to import new port, instead of updating existing port databases/msql to new version? -- Pav Lucistnik <pav@oook.cz> <pav@FreeBSD.org> An arrow (+0,+0) {@f0} finds a mark. It dies.
Hi. Sat, 29 May 2004 16:27:58 +0200, you wrote: > What's the reasons to import new port, instead of updating existing port > databases/msql to new version? msql3 is not contains w3-msql and other tools. Not delete msql2 in ports collection - i am supporting this port too. --anray
Responsible Changed From-To: freebsd-ports-bugs->sem Take it.
State Changed From-To: open->repocopy Repocopy request.
Responsible Changed From-To: sem->portmgr Repocopy request.
State Changed From-To: repocopy->open Please specify exactly what you need copied when moving the port into the repocopy state.
Responsible Changed From-To: portmgr->sem Please specify exactly what you need copied when moving the port into the repocopy state.
State Changed From-To: open->repocopy repocopy databases/msql -> databases/msql3
Responsible Changed From-To: sem->portmgr repocopy request: databases/msql -> databases/msql3
State Changed From-To: repocopy->open Repo-copy completed.
Responsible Changed From-To: portmgr->sem Repo-copy completed.
State Changed From-To: open->closed Commited, thanks! pkg-plist smoothed.