On Aug 15, 2007, at 6:55 PM, Michael Bayer wrote:
> thats definitely not going to work right now. I added feature > enhancement # 740, currently its milestone 5 unless we start > getting more time for some of these things. put primary_key on your > Table for now. I've disabled the eager loading of related objects (lazy=False) for now which apparently seem to work around the lack of pk in Table (and, surprisingly, results faster selects)... If this doesn't work out well I'll probably "cheat" SA and declare a PK constraint but remove it manually on the real table. Unless I can think of something better... Thanks for looking into it. Alberto --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
