OnQueryError not being called in r38 Linux (Debian 7 x86)

[karimcambridge]

public OnQueryError(errorid, error[], callback[], query[], connectionHandle)
{
    printf("[OnQueryError (%d, %s, %s)]: Query: %s", errorid, error, callback, query);
    switch(errorid)
    {
        case CR_COMMAND_OUT_OF_SYNC: {
            printf("[MySQL: Error - Callback; %s] - Commands Out Of Sync For - Query: %s", callback, query);
        }
        case ER_UNKNOWN_TABLE: printf("[MySQL: Error - Callback; %s] - Unknown table '%s' Query: %s", callback, error, query);
        case ER_SYNTAX_ERROR: printf("[MySQL: Error - Callback; %s] - Something is wrong in your syntax - Query: %s", callback, query);
        case CR_SERVER_GONE_ERROR, CR_SERVER_LOST, CR_SERVER_LOST_EXTENDED: mysql_reconnect();
    }
    return 1;
}

[00:00:45] [ERROR] CMySQLQuery::Execute[] - (error #1050) Table 'A_Backup_2014_4_7' already exists
[00:00:45] [ERROR] CMySQLQuery::Execute[] - (error #1062) Duplicate entry '1' for key 'PRIMARY'
[02:42:13] [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 '5' at line 1
[04:21:10] [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 '5' at line 1
[12:51:55] [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 '5' at line 1
[22:45:46] [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 '5' at line 1
[01:23:47] [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 '5' at line 1
[11:41:17] [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 '5' at line 1
[12:03:50] [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 '5' at line 1
[13:40:01] [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 '5' at line 1
[16:38:16] [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 '5' at line 1
[17:14:37] [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 '5' at line 1
[17:24:49] [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 '5' at line 1
[21:09:17] [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 '5' at line 1
[08:28:59] [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 '5' at line 1
[16:46:11] [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 '5' at line 1
[17:00:13] [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 '5' at line 1

** it works on windows appearantly

[karimcambridge]

I also have an issue, since this isn't being called I can't find simple errors like above and

[04:58:38] [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
[05:22:01] [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 '5' at line 1
[08:07:26] [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
[11:16:23] [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
[11:41:11] [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 '5' at line 1

without enabling a VERY HEAVY mysql LOG and I realy don't want to do that as I might not be even able to open the file due to my 512 RAM lol

[lorencpekaj]

@KAR2K Yeah hell. I'm receiving like 3 of those weekly, but can't seem to identify them properly... Can errors be more elaborate?

[maddinat0r]

I've already planned to log line numbers (line of code) within the log (see issue #18), but this enhancement requires Zeex's PAWN compiler patches. There aren't much options on how to improve error messages, I'll have to think about a better way. I'll create a special issue (#19) for that, you can suggest some improvements there if you want.

[karimcambridge]

I use zeex's compiler patches. and you can detect that compiler with the changed __Pawn value or something.

The real problem is OnQueryError isn't being called on linux, if that was called we would know which query!

[lorencpekaj]

@maddinat0r Would it be stupid to ask whether the query itself can be printed on the line?

[maddinat0r]

@KAR2K yes, that's of course the main problem here.
@zeelorenc I could just print all information available (query, callback name, error id, ...) if an error occurs. However, there is still the option to customize error messages via the OnQueryError callback. The only limitation is, that only query errors are handled in this callback, but queries are pretty much the main cause of errors.

[maddinat0r]

@KAR2K I couldn't reproduce your issue on Debian Wheezy i686. Could you please create a small script which reproduces your issue?

[karimcambridge]

I don't really know, it's just my main mode.

Does anyone else have this issue?

[maddinat0r]

Whoops, I made a mistake, I didn't saw that you weren't using a callback. The code says that OnQueryError will be called if there is a callback specified and the query is threaded, but you didn't specified any callback and that's why OnQueryError wasn't called.
Sometimes I really wonder why I'm writing such code. I'll remove that callback check.