On 4/5/13, Gary Martin <[email protected]> wrote:
> On 05/04/13 20:28, Branko Čibej wrote:
[...]
>>>>
>>> That is not too surprising if they do not parse the sql statements to
>>> determine whether quotes are for "quoted identifiers" or 'string
>>> constants' - it is not completely unreasonable to call these
>>> programmer errors as PostgreSQL follows the standards while SQLite
>>> (and possibly MySQL?) relaxes these quoting rules. I found a
>>> suggestion that it you shouldn't continue to rely on this for future
>>> versions of SQLite either.
>> MySQL has to be explicitly put into strict ANSI mode in order to follow
>> the quoting rules. It's not by default.
>
> Well, as long as non-strict mode doesn't do something crazy like only
> accept quoting in exactly the opposite form, then we can't go far wrong!
> These relaxed interpretations are encouraging us to be a bit too relaxed
> about getting the SQL right.
>
>>
>>> I've just found some more problems associated with the postgres
>>> backend so I will be looking into this kind of thing for a bit!
I'm not completely sure of whether this message is related to the
previous thread or not , but it's worth checking .
Notice [1]_ that there are some failures (regressions ?) in tests.db
sub-package .
.. [1] Bloodhound multiproduct : test report 5/4/2013
(http://pastebin.com/0ZQCprDv)
--
Regards,
Olemis.
