"manager" is an attribute on InstanceState that is set at construction time, and is never changed thereafter. Looking at your error more closely, its not that "manager" is None, its not even present. That can only happen if something del'ed the "manager" attribute, the InstanceState somehow went through some failed deserialization process, or some gc-related activity had occurred involving that object. I'm not aware of any simple way to produce that effect. it certainly has nothing to do with the specifics of your mappings.
On May 7, 2010, at 10:14 AM, andrew cooke wrote: > > As far as I know, I'm doing nothing that complex. I am creating a > pile of mapped objects in Python and then dumping them to the > database. The most likely cause is that a field is None, or of the > incorrect type in some way, I would have guessed. > > Andrew > > On May 7, 9:56 am, Michael Bayer <mike...@zzzcomputing.com> wrote: >> this looks like some kind of serialization issue. are you deserializing >> instances before mappers have been compiled ? if you upgrade to 0.6, this >> will raise an error immediately at the point at which it occurs. > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To post to this group, send email to sqlalch...@googlegroups.com. > To unsubscribe from this group, send email to > sqlalchemy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sqlalchemy?hl=en. > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
