.
This approach is of course completely impossible to pass upstream.
Rhett
On Tue, Dec 14, 2010 at 8:21 AM, Michael Bayer wrote:
> There's really two concepts of "isolation level" at play.
>
> The "isolation_level" parameter in SQLA is usually linked to
> databa
inate the need to make these queries ? Though we
of course don't open new connections often, it does happen and adding
this overhead for information that probably shouldn't change seems
unnecessary.
(MySQL 5.0.x, sqlalchemy 6.0beta)
Rhett
--
You received this message because you are subscri
myself quite clearly. build_id_column() is
doing exactly what the docs are saying to do,
just trying to abstract out that pattern since it will be used on
every single object in our system, often for multiple cols.
Rhett
--
You received this message because you are subscribed to the Google
On Wed, Apr 21, 2010 at 6:35 AM, Michael Bayer wrote:
> Rhett Garber wrote:
>> This would be much easier, I could potentially be what we go with. I
>> think this is similar to my 'original implementation'
>> I just found the syntax to be a bit bothersome since the p
On Tue, Apr 20, 2010 at 4:32 PM, Michael Bayer wrote:
>
> On Apr 20, 2010, at 7:06 PM, Rhett wrote:
>
>> I've run into some difficulty getting the ORM to fit into an existing
>> code base with some, I suppose, non-standard conventions.
>>
>> One of the co
nt register_descriptor() to achieve.
This is all getting very complicated.
Is there any other way to get some control over getting of a column ?
AttributeExtension handles the setting, I think,
but there is no interface for getting.
I'm hoping I'm missing something.
(Using sqlalchemy 6be
