On Friday 22 December 2006 14:31, Michael Bayer wrote:
when i put PKs on the table, it worked fine. so that you get the error is disturbing to me since I have tried to insure that there are no paths into a Mapper that wont compile it first. It makes sense that you might have problems I dont, since im testing on OSX whereas you are on linux, and one thing ive noticed about linux is that Python dictionaries produce a very different ordering than whatever you get on OSX (and therefore all kinds of ordering-dependent bugs pop up when i test on linux that dont come up on OSX). so i think there might be a bug here...im going to add a ticket to remind myself to test on linux later.
The only other difference beyond linux (I suppose) is that I am using Postgres 8.2. This is new enough that I don't think many are using it. I am also seeing odd behavior when running under pylons using straight sqlalchemy and BoundMetaData that you suggested in an earlier thread might be related to a postgresql version change.
Sean --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
