Yes, of course. ;-) But is it possible not to map certain columns? Preferably, without using a select and listing every single column that should be present?
Foreign key columns are obvious candidates to be left out, because the relations should be used instead. Currently, I always rename them into private attributes (with a leading underscore). BTW, the mapper might want to check that keys are nonempty strings and no two columns are mapped to the same attribute (currently, the last one wins). Best regards Klaus On 2 Jul., 18:12, Michael Bayer <[EMAIL PROTECTED]> wrote: > On Jul 2, 2007, at 10:40 AM, klaus wrote: > > > > > I would rather ask: How can this behavior be avoided? Is it possible > > to mark some columns as read-only/no-write-back? > > just remove the primary key columns of the "non-write" tables from > the columns clause of the select. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
