No, this is a new bug report, not the related reports. :-)
Because I can't add notes to existing bug report. I can't even relate
them. No input controls available for that purpose. :( Or am I missing
something? *I told you I'm new to mantis system* :D
-Bee-
has Bee.ography at:
http://beeogr
Bee schreef:
Just note in the related reports that in your relevant branch (2.2.1 +
exact
svn revision) the problem still persists.
Done: 0010272
No, this is a new bug report, not the related reports. :-)
Vincent
___
fpc-pascal maillist - fpc-p
Just note in the related reports that in your relevant branch (2.2.1 + exact
svn revision) the problem still persists.
Done: 0010272
-Bee-
has Bee.ography at:
http://beeography.wordpress.com
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.or
> > Yes, but afaik there already is one. Walk the database component bugreports
> > to find out.
>
> I found 0010148 and 0009763 are related to my problem. Can we have the
> patch back-ported to 2.2.1?
Just note in the related reports that in your relevant branch (2.2.1 + exact
svn revision) the
Yes, but afaik there already is one. Walk the database component bugreports
to find out.
I found 0010148 and 0009763 are related to my problem. Can we have the
patch back-ported to 2.2.1?
-Bee-
has Bee.ography at:
http://beeography.wordpress.com
_
> Some complex queries are failed to be executed on mysql50 using fpc
> 2.2.1 (rev 9278). Complex queries are queries that involving aggregate
> query clauses (group by, max, etc). Setting ParseSQL to true or false
> doesn't solve the problem.
>
> Same queries run fine on fpc 2.2.0.
>
> Should
Hi all,
Some complex queries are failed to be executed on mysql50 using fpc
2.2.1 (rev 9278). Complex queries are queries that involving aggregate
query clauses (group by, max, etc). Setting ParseSQL to true or false
doesn't solve the problem.
Same queries run fine on fpc 2.2.0.
Should I re
