Re: [sqlalchemy] Nested bundles, labels and Ambiguous column name

On 4/9/15 1:50 PM, Jacob Magnusson wrote: I have this case with a bundle that looks something like this: |primate_bundle = Bundle( 'primate', Primate.name, Bundle('wooden_tool', *[ WoodenTool.id, WoodenTool.name, WoodenToolCategory.name.label('category'), ]), Bundle('solid_tool', *[

Re: [sqlalchemy] Nested bundles, labels and Ambiguous column name

Thanks for the quick reply Michael. I would love to hear what you can find out about it. I have what I think is a pretty horrible and dirty “solution”. But it *seems* to work. What I’ve done is to assign the key attribute of columns like this: from collections import namedtuple

[sqlalchemy] Re: Nested bundles, labels and Ambiguous column name

Thanks for the quick reply Michael. I would love to hear what you can find out about it. I have what I think is a pretty horrible and dirty “solution”. But it *seems* to work. What I’ve done is to assign the key attribute of columns like this: from collections import namedtuple

Re: [sqlalchemy] Eagerly loading backrefs

Thanks for the quick response! I implemented your suggestion and I think that's perfectly fine for me, as there's no use case for loading ConfigParam instances on their own. cheers Am Mittwoch, 8. April 2015 17:16:44 UTC+2 schrieb Michael Bayer: On 4/8/15 3:22 AM, Sebastian Eckweiler

[sqlalchemy] Nested bundles, labels and Ambiguous column name

I have this case with a bundle that looks something like this: primate_bundle = Bundle( 'primate', Primate.name, Bundle('wooden_tool', *[ WoodenTool.id, WoodenTool.name, WoodenToolCategory.name.label('category'), ]), Bundle('solid_tool', *[

[sqlalchemy] GeoAlchemy2 mutation tracking on Geometry Column?

Is there some way to implement mutation tracking on a sqlalchemy2 Geometry (POLYGON) Column? Can I just wrap it in a MutableDict can I? -- You received this message because you are subscribed to the Google Groups sqlalchemy group. To unsubscribe from this group and stop receiving emails from

Re: [sqlalchemy] Nested transaction rollback does not undo changes to instances

(Chris's colleague here) On Thursday, 2 April 2015 17:23:13 UTC+1, Michael Bayer wrote: this issue is fixed for 0.9.10 and 1.0.0b5, you can test now using either latest master or the rel_0_9 branch. Just wanted to say thank you very much for the prompt fix; I continue to be amazed at

[sqlalchemy] Constraint naming conventions and MySQL's 64 character name limit

Hello All! I'm facing the well known problem of maintaining constraints, when using sqlalchemy (v0.9.8), alembic (v0.7.4) and MySQL (v5.5.41) on Ubuntu (v14.04.2). I'm talking specifically about these two links: o