Thanks for the help. I almost have this up and running, but I have
found one preplexing issue.
My current code base has a very extensive test suite. As part of this
test suite, I have my test fixtures setup and teardown databases,
mappers, and just about every SA related. This is meant to
On May 5, 2008, at 5:04 PM, Allen Bierbaum wrote:
Is there some way to clear the declarative layer and have it
regenerate all automatically created metadata and mappers?
not as of yet but this could be done.
but if you are using declarative, that implies that for a class X
there is only
On Mon, May 5, 2008 at 4:29 PM, Michael Bayer [EMAIL PROTECTED] wrote:
On May 5, 2008, at 5:04 PM, Allen Bierbaum wrote:
Is there some way to clear the declarative layer and have it
regenerate all automatically created metadata and mappers?
not as of yet but this could be done.
but
So, if I understand this right, I could import a base module that
does a lazy creation of the Base class with a metadata object and then
just use that base class everywhere I need it for the declarative
class definitions. Then at a later time (before I use the mapped
classes), I could go and
On Apr 28, 2008, at 5:42 PM, Allen Bierbaum wrote:
So, if I understand this right, I could import a base module that
does a lazy creation of the Base class with a metadata object and then
just use that base class everywhere I need it for the declarative
class definitions. Then at a later
On Apr 27, 2008, at 8:25 AM, Allen Bierbaum wrote:
The problem that as I understand it, to use declarative, you can't
import an module that defines a table-based object until after some
initialization code has been run to connect to a database and create a
'Base' class for the declarative
