Page 1 of 1
Anyone is checking the Bugs site?
Posted: 21.02.2007, 15:08
by waheed
I have posted a problem to the Bugs site as instructed by the Admins here. But no one seemed to be able to solved it.
http://zeosbugs.firmos.at/view.php?id=16
Posted: 21.02.2007, 17:34
by mdaems
OK Waheed,
As this is a mysql problem I could give it a try. Can you also show the problem in a regular program? I have no clue how to debug the working IDE ... So please help me if you can.
The reason why bugfixing is so slow: there are no other developers left who can dedicate some time to the project. I try to give some attention to the mysql bugs, but can just do them one at a time (and I don't have to much spare time to devote to it). An extra problem : I have no experience with other databases. So these bugs I have to leave for others (who are absent). Please let this be an invitation to everybody to have a look at the bug list and look if there are no problems you can have a look at.
I promise to integrate fixes provided by you if they look somewhat reasonable and don't break up other stuff at first sight.
Mark
A sample Delphi is uploaded
Posted: 22.02.2007, 09:00
by waheed
I have uploaded a sample program to Bugs site. Hope it helps finding the problem.
While creating the sample I noticed another problem with this bug, I cannot update the problem field in the query with this function, but I could update other fields in the query!!!
Posted: 22.02.2007, 11:49
by mdaems
I'll have a look at it (but don't know when yet).
I know I have recently solved a bug where there was confusion about fieldtypes, functions and aliases.
(See
http://zeosbugs.firmos.at/view.php?id=3 )
That was a nasty one. I hope it's not the same one and secondly I hope I remember enough about it to avoid I have to redo all learning.
Mark
Posted: 25.02.2007, 00:26
by mdaems
Waheed , thanks for the test program. It helped a lot to make sure the error would reproduce.
The reason was similar to the bug I told you about (Mantis Bug 3). it was in the same function, so I found the problem within 2 hours.
Apparently somebody liked skipping characters when he wrote the SQLAnalyser. In this case the parser did not see the opening bracket in "get_full_no(no, norest, mktype) as full_no,". And the commas between the brackets made it too confusing as the parser didn't know they were part of that one selected field. So he splitted like this: norest|mktype|get_full_no|norest|full_no|no.
Please test and send me a little confirmation
Sorry, but this solution will not yet be included in 6.6.1-beta version (too late). It's in SVN testing branch revision 221.
Posted: 25.02.2007, 10:06
by waheed
It is fixed. Thanks