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 you select are "embedded" in the from clause while what
you want is modify what is selected "before" the from clause, whether
this is columns or more complex expressions.
--
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, y, z properties...but the rest just get set up
normally.
so waht you want is this:
mapper(X, table, properties={
'x':table.c.x,
'y':table.c.y
}, explicit_columns=True)
which means, set up x and y, but dont go setting up everything else
inside of table.c (i.e., no z).
9 messages in com.googlegroups.sqlalchemy[sqlalchemy] Re: Single table inherit...
.py