On 05.04.2013 18:03, Gary Martin wrote: > On 04/04/13 17:37, Olemis Lang wrote: >> On 4/4/13, Gary Martin <[email protected]> wrote: >>> On 02/04/13 12:34, Jure Zitnik wrote: >>>> On 3/29/13 11:58 AM, Gary Martin wrote: >>>>> Yeah, looking forward to it! >>>>> >>>>> On 29/03/13 10:43, Andrej Golcov wrote: >>>>>> +1 to go for it. >>>> fyi, branch BEP-0003 (multi product) has been merged to trunk in >>>> r1463489, reintegrated branch has been removed in r1463491. >>>> >>>> Cheers, >>>> Jure >>>> >>>> >>> It looks like there may be a few issues that will turn up with >>> PostgreSQL backends with the new multi-product setup. I have already >>> found problems with installation that I hope I have fixed now for >>> https://issues.apache.org/bloodhound/ticket/497 but there are bound to >>> be more. >>> >> I see some test cases for PostgreSQL ... >> >> {{{ >> #!sh >> >> $ ls bloodhound_multiproduct/tests/db/ >> api.py cursor.py __init__.py mysql.py postgres.py util.py >> >> }}} >> >> ... but do not seem to fail ... o.O >> > > 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. > 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 suggest all testing should be done with at least two databases, pgsql being one of them; although for actual installations, of the three options mentioned, I'd only ever recommend PostgreSQL. -- Brane -- Branko Čibej Director of Subversion | WANdisco | www.wandisco.com
