[maddinat0r]

Quote:

Originally Posted by kadaradam Can you please add a more accurate error, warning logging? Because there's not much info in these: Код: [11:56:48] [ERROR] CMySQLQuery::Execute[] - (error #1064) You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1 [20:35:25] [WARNING] CMySQLResult::GetRowData - invalid row ('0') or field index ('0') And also would be cool to add year, month and day to the logging.

R40.

Quote:

Originally Posted by BRICS Does it close all unclosed connections automatically? Is it necessary to use mysql_close() every time I exit server / make new connection (to the same db)? I have FS using MySQL BlueG to install on server using this too. If server's connection and fs' connection lead at the same database, their handle IDs will be matched, so when fs' connection is closing another's closing too. How can I prevent it?

The plugin closes all connection on proper server exit.
If you call

Код:

mysql_option(DUPLICATE_CONNECTIONS, true);

before creating a connection, connections with matching credentials won't be detected as duplicate connections (thus every created connection will be unique).

Quote:

Originally Posted by Johurt "Rida" save 1.174e.5 instead of 117415. Printf show correct value (117415). I use MySQL R39-3. It is bug? EDIT: This problem only with mysql_format, with format all ok.

This is not really a bug, but part of the IEEE 754 floating point standard. This is just an other way of representing a number. Try reading in that "weird" float value and check if it outputs the correct float value - it should.