MySQL Manual
1 General Information
- 1.10 How MySQL Compares to Other Databases
- 1.10.1 How MySQL Compares to
mSQL- 1.10.1.1 How to Convert
mSQLTools for MySQL - 1.10.1.2 How
mSQLand MySQL Client/Server Communications Protocols Differ - 1.10.1.3 How
mSQL2.0 SQL Syntax Differs from MySQL
- 1.10.1.1 How to Convert
1.10.1.2 How mSQL and MySQL Client/Server Communications Protocols Differ
There are enough differences that it is impossible (or at least not easy) to support both.
The most significant ways in which the MySQL protocol differs
from the mSQL protocol are listed here:
- A message buffer may contain many result rows.
- The message buffers are dynamically enlarged if the query or the result is bigger than the current buffer, up to a configurable server and client limit.
- All packets are numbered to catch duplicated or missing packets.
- All column values are sent in ASCII. The lengths of columns and rows are sent in packed binary coding (1, 2, or 3 bytes).
- MySQL can read in the result unbuffered (without having to store the full set in the client).
- If a single read/write takes more than 30 seconds, the server closes the connection.
- If a connection is idle for 8 hours, the server closes the connection.
