[sqlalchemy] Re: Interned tring

2009-07-03 Thread limscoder
with String properties? > > > On Jun 28, 2:20 pm,limscoder wrote: > >> Hi, > > >> Is there a way to automatically get an interned string for objects > >> with String --~--~-~--~~~---~--~~ You received this message because you are su

[sqlalchemy] Re: Interned tring

2009-06-28 Thread limscoder
What I meant to say was: Is there a way to automatically get interned strings when querying objects with String properties? On Jun 28, 2:20 pm, limscoder wrote: > Hi, > > Is there a way to automatically get an interned string for objects >

[sqlalchemy] Interned tring

2009-06-28 Thread limscoder
Hi, Is there a way to automatically get an interned string for objects with String --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com

[sqlalchemy] Re: 5.2 to 5.3 base-class/sub-class handling change

2009-05-21 Thread limscoder
Thanks. I was trying to map both classes to the same table, and that was causing problems! On Apr 10, 1:43 pm, "Michael Bayer" wrote: > limscoderwrote: > > > In 5.2 I was able to map a base-class, and sub-classes would > > automatically be persisted as the base type. In 5.3 I get an > > Unmappe

[sqlalchemy] 5.2 to 5.3 base-class/sub-class handling change

2009-04-10 Thread limscoder
In 5.2 I was able to map a base-class, and sub-classes would automatically be persisted as the base type. In 5.3 I get an UnmappedInstanceError when trying to persist an object of the sub- class type. I didn't see anything about this change in the changelog. Is there a way to get the <5.3 behavior