[sqlalchemy] arbitrary information for sa objects

2008-05-03 Thread alex bodnaru
hello friends, however sa stands at the model foundation of an application, i'd be interested to add additional information to some columns/tables/keys. is there a way to insert arbitrary information for sa objects? thanks in advance, alex

[sqlalchemy] Re: arbitrary information for sa objects

2008-05-03 Thread alex bodnaru
i read info is such a table option, but i'm not sure it's not deprecating? alex bodnaru wrote: hello friends, however sa stands at the model foundation of an application, i'd be interested to add additional information to some columns/tables/keys. is there a way to insert arbitrary

[sqlalchemy] Ordered merge of shard results (update)

2008-05-03 Thread Kyle Schaffrick
On Thu, 1 May 2008 12:20:39 -0400 Michael Bayer [EMAIL PROTECTED] wrote: at first the second method seemed a little hacky to me, but now that i think about it, we're in the sharded query so removing the extra entity is not a big deal.The first method is probably not as fragile as

[sqlalchemy] Re: arbitrary information for sa objects

2008-05-03 Thread Paul Johnston
Alex, The info bucket is available just on columns at the moment, and it is a supported feature. I think we're open to adding it to other types, such as tables, if someone has a requirement. My desire for this was exactly the same as yours - the SA model serving as the authoritative master

[sqlalchemy] Re: arbitrary information for sa objects

2008-05-03 Thread alex bodnaru
hi paul, thanks for your attention. http://www.sqlalchemy.org/docs/04/sqlalchemy_schema.html#docstrings_sqlalchemy.schema_Table shows info as a parameter in the kwargs to a table. it would be great if there were info for other objects too. please point me to the column info setting. best

[sqlalchemy] Re: Ordered merge of shard results (update)

2008-05-03 Thread Michael Bayer
On May 3, 2008, at 7:03 AM, Kyle Schaffrick wrote: The one thing I haven't checked yet is if inheritance breaks the meth = _generative(__foo_condition)(meth) call, since it's not clear to me that the __foo_condition names are bound inside ShardedQuery's definition. I haven't