On Jun 6, 2007, at 12:49 PM, Eric Ongerth wrote:
> > Yeah. My problem has been solved by altering the tables... > skiboots.c.size is now skiboots.c.skiboot_size, and skis.c.size is now > skis.c.ski_size. > > Is there a way I could avoid that, making use of the use_labels=True > parameter on select()? I've been trying to work out how to rewrite my > item_join to do that, so that identically columns in child tables > would not collide. the polymorphic_union isnt going to work so great with use_labels. thats a very problematic function as far as column naming conventions and its not very open to trickery (which is why you can, of course, build your own UNION manually). --~--~---------~--~----~------------~-------~--~----~ 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 To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
