Well, I looked at this a bit last night, and recent TG releases don't enforce a foreign key between the visit and visit_identity tables (in fact, it looks like there was a foreign key, but it has been commented out). So, I suspect most people aren't seeing this bug because of that, and that perhaps you are working from a pretty old model declaration for visit_identity (or you uncommented the foreign key).
I really can't say whether it is a tg/identity bug or a TurboGears bug. IF all the changes occur in the same session, it seems like SqlAlchemy should be smart enough to save the key values first, then the foreign keyed values, and it would be a SA bug. But I'm not familiar enough with the database code to be able to say for sure if that's really what's going on. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
