Lee McFadden wrote: > I'm now getting the same thing, although I wasn't last night when > helping someone in IRC. Have you also upgraded to SQLAlchemy 0.3 or > installed SA since 0.3 was released? > > Lee
I was using SA 0.28, which came with TG 1.01b. I have since performed `sudo easy_install -U -Z SQLAlchemy` to get SA 0.30 and the problem is still there. I also get a muthaload of debugging output! But no fix. What's odd though is that my custom objects using one_to_many seem to work fine. If Jonathan LaCour (sp?) has no clues I'll set up my own many_to_many and see if it makes a difference. One thought I had is that I'm using MySQL 5, and although SA seems to identify its relational columns with a foreign_key attribute (little too automagic for my liking), MySQL doesn't preserve relations without manual intervention. However, starting with a fresh SQLite database yields the same result, so that last paragraph is now a bit redundant. -Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
