On 12/28/10 20:54 , Michael Bayer wrote:
On Dec 28, 2010, at 2:22 AM, Wichert Akkerman wrote:
On 2010-12-28 08:18, Hong Minhee wrote:
I don’t know why setuptools provides pkg_resources, implements another
incompatible way to declare namespace packages, additionally in spite of
existence of
Yeah this is what I'm seeing, that top level packagenames are used. I.e. I
would just say, Use sqlalchemycontrib as your package name, that's what
everyone should use. It would appear this approach means nothing needs to
happen at all witihin sqlalchemy core.
On Dec 29, 2010, at 1:24 AM,
On 12/29/10 16:45 , Michael Bayer wrote:
Yeah this is what I'm seeing, that top level packagenames are used. I.e.
I would just say, Use sqlalchemycontrib as your package name, that's
what everyone should use. It would appear this approach means nothing
needs to happen at all witihin sqlalchemy
On Dec 29, 2010, at 11:02 AM, Wichert Akkerman wrote:
On 12/29/10 16:45 , Michael Bayer wrote:
Yeah this is what I'm seeing, that top level packagenames are used. I.e.
I would just say, Use sqlalchemycontrib as your package name, that's
what everyone should use. It would appear this approach
Howdy all,
I'm relatively new to SQLAlchemy, so I hope this isn't too silly of a
question/issue, but I'm having some issues with a TypeDecorator type
I've created and am seeking advice.
I have a situation where I'd like to automatically convert hex strings
(in this case they are actually MD5
The only unusual thing about the app is the usage of a binary field as a
primary key. I'm not even sure postgresql supports bytea as a PK, but that is
a very likely candidate for where things are going wrong.If the bytea
actually works as a PK, the ORM may be tripping on it. Try
Well, it looks like Postgres doesn't mind bytea as a PK (the table
definition shows that it's using it) so I don't think that is the
problem. The objects themselves seem fine too, it was just the string
representation that was an issue (AFAICT).
I did figure out a workaround however (although
Looking at the events for instances.
The on_expire passes a list of attributes being expired but the on_refresh does
not have a list of attribute being refresh.
Can the list of attribute being refreshed be add to on_refresh event ?
I am looking to move from using mapperextension to instance
On Dec 29, 2010, at 5:04 PM, Mike Bernson wrote:
Looking at the events for instances.
The on_expire passes a list of attributes being expired but the on_refresh
does not have a list of attribute being refresh.
Can the list of attribute being refreshed be add to on_refresh event ?
this
