On Jul 11, 6:14 pm, Michael Bayer <[email protected]> wrote: > On Jul 11, 2010, at 5:39 AM, Ste wrote: > > > What I still don't understand is, that if I run the same query in pdb > > immediately after the raise, I get back > > None (which is what I would expected). > > I seem to recall MySQL had some bugs with joins, this log output definitely > looks like one: > > SELECT wiki_page.type AS > wiki_page_type, wiki_page.id AS wiki_page_id, problem.id AS > problem_id, wiki_page.name AS wiki_page_name, wiki_page.content AS > wiki_page_content, wiki_page.timestamp AS wiki_page_timestamp, > wiki_page.creator AS wiki_page_creator, wiki_page.creator_ip AS > wiki_page_creator_ip, problem.discussion_id AS problem_discussion_id > FROM wiki_page INNER JOIN problem ON wiki_page.id = problem.id > WHERE wiki_page.id IS NULL > LIMIT 0, 1 > ('wiki_page_type', 'wiki_page_id', 'problem_id', 'wiki_page_name', > 'wiki_page_content', 'wiki_page_timestamp', 'wiki_page_creator', > 'wiki_page_creator_ip', 'problem_discussion_id') > ('problem', 2L, 2L, 'Double name test', 'This is a problem for the double > name test.', datetime.datetime(2010, 7, 11, 11, 30, 57), None, '127.0.0.1', > 1L) > > the result returned is clearly not what the query asks for. You might try > using the latest MySQL version, or poke around in their bugtracker for issues > regarding joins.
I tried it with 5.1.48 with the same result. The development release 5.5.3 passes the test without this problem. So apparently I have to wait and see whether 5.1.49 fixes this bug or change my code... Thanks for the help! -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
