Re: [sqlalchemy] Re: negative implications of using multiple declarative Base classes

2010-08-24 Thread Chris Withers
avdd wrote: 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). Indeed, but I suspect there's more to it than

Re: [sqlalchemy] Re: negative implications of using multiple declarative Base classes

2010-08-24 Thread Michael Bayer
On Aug 24, 2010, at 3:04 AM, Chris Withers wrote: avdd wrote: 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

[sqlalchemy] Re: negative implications of using multiple declarative Base classes

2010-07-08 Thread avdd
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: