Michael Bayer wrote:
> well i can just put the string thing in, and i generally wont mention
> it much.
Thats fine with me.
> if we're putting in strings, shouldnt people be able to specify
> modulenames as well ? i.e. "somemodule.SomeClass" ?
Sure, that would work fine. In ActiveMapper, I wil
well i can just put the string thing in, and i generally wont mention
it much.
if we're putting in strings, shouldnt people be able to specify
modulenames as well ? i.e. "somemodule.SomeClass" ?
On Jun 15, 2006, at 12:52 PM, Jonathan LaCour wrote:
> Michael Bayer wrote:
>> well im just a l
Michael Bayer wrote:
> well im just a little concerned that it gives people another way to
> break their code.now they can have two classes of the same name,
> which will have to be in some global dictionary somewhere to match
> the strings up with the classes/mappers, then itll either silently
On Jun 14, 2006, at 8:39 PM, Jonathan LaCour wrote:
> I am still having to do a lot more checking than I would like because
> the 'relation' constructor takes in a class or mapper, and I have to
> wait for the class or mapper to *exist* before creating it. Any
> chance
> of being able to pass
Michael Bayer wrote:
>> Does this changeset make it so that ActiveMapper doesn't have to
>> jump through a bunch of hoops to make sure that tables/mappers are
>> processed in a particular order for relationship dependencies?
>
> probably. it would be very helpful for you to get the latest trunk and
On Jun 14, 2006, at 1:50 PM, Jonathan LaCour wrote:
> Does this changeset make it so that ActiveMapper doesn't have to jump
> through a bunch of hoops to make sure that tables/mappers are
> processed
> in a particular order for relationship dependencies?
>
probably. it would be very helpful
Michael Bayer wrote:
> the latest trunk uses deferred mapper compilation and solves this
> problem (ticket #194 in trac: http://www.sqlalchemy.org/trac/ticket/
> 194)
Does this changeset make it so that ActiveMapper doesn't have to jump
through a bunch of hoops to make sure that tables/mappers ar
the latest trunk uses deferred mapper compilation and solves this
problem (ticket #194 in trac: http://www.sqlalchemy.org/trac/ticket/
194 )
On Jun 13, 2006, at 5:44 PM, Randall Smith wrote:
> I've got 200+ tables with lots of relationships that I'm trying to map
> SQLAlchemy to. I'm writin
I've got 200+ tables with lots of relationships that I'm trying to map
SQLAlchemy to. I'm writing a code generator to create the classes,
mappings, etc. A problem that I don't see a simple solution to is
writing the mapper code in the proper order. If I attempt to map one
class to another th
9 matches
Mail list logo
