You can use it sure. It examines the constructor of the class and attempts to generate a repr() that displays keyword parameters which deviate from the defaults.
Those areas where we don't use it in schema.py are where we have been using a certain comprehensive repr() for a long time like that of Column. On Aug 30, 2011, at 1:35 PM, Fayaz Yusuf Khan wrote: > Hi, I'm trying to write a good __repr__ for this subclass. On reading your > code, I saw that several of your __repr__ definitions depend on > sqlalchemy.util.generic_repr (and several don't). Is it a public API? Don't > see much documentation for it anywhere. Could you explain about its proper > usage? > > On Monday 08 Aug 2011 12:17:16 AM Michael Bayer wrote: >> Sorry I didn't look closely. Yes when you subclass FKC overriding >> _set_parent() to perform additional steps is one way to establish >> on-connect details. Another is to use >> event.listen(ImplicitForeignKeyConstraint, "after_parent_attach"), it >> would be a little more of the public API. > > -- > Fayaz Yusuf Khan > Cloud developer and designer > Dexetra SS, Kochi, India > fayaz.yusuf.khan_AT_gmail_DOT_com > fayaz_AT_dexetra_DOT_com > +91-9746-830-823 -- 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.
