On 7/28/07, Michael Bayer [EMAIL PROTECTED] wrote:
those are fine with me. if someone could add a ticket and/or
implement that would be helpful.
http://www.sqlalchemy.org/trac/ticket/696
--
Gaëtan de Menten
http://openhex.org
--~--~-~--~~~---~--~~
You
On Jul 27, 2007, at 4:03 PM, Gaetan de Menten wrote:
so do you just want explicit_columns=True so that no auto-grabbing
of columns occurs ?
I don't know exactly what I want (or maybe it's just I don't care how
it's done). It's just that I found it suboptimal that in some cases
the columns
On 7/27/07, Michael Bayer [EMAIL PROTECTED] wrote:
On Jul 27, 2007, at 4:03 PM, Gaetan de Menten wrote:
so do you just want explicit_columns=True so that no auto-grabbing
of columns occurs ?
I don't know exactly what I want (or maybe it's just I don't care how
it's done). It's just
yeah look, this is how it works. your table has x, y, and z.
you set up a mapper. x, y and z all become ColumnPropertys on
your mapper, without you doing anything, i.e. no properties dict.
if you set up a properties dict, columns which you map
explicitly will override the normal x,
those are fine with me. if someone could add a ticket and/or
implement that would be helpful.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To post to this group, send email to
