I'm glad you brought this up. It seems to me that the the declarative instrumentation keys classes by their unqualified class name, precluding using the same class name for different declarative subclasses (ie, in different modules).
On Jul 9, 12:01 pm, Randy Syring <ra...@rcs-comp.com> wrote: > I have been, naively it seems, using multiple declarative Base classes > in my webapp. They all share the same metadata object. > > I have found one negative ramification of this, which is that string > references (like what can be used in relation()) won't find the object > if they are not using the same Base. Are there others? -- 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.
