I would rather ask: How can this behavior be avoided? Is it possible to mark some columns as read-only/no-write-back?
Best regards Klaus On 2 Jul., 16:35, Andreas Jung <[EMAIL PROTECTED]> wrote: > --On 2. Juli 2007 14:22:06 +0000 Michael Bayer <[EMAIL PROTECTED]> wrote: > > > > > On Jul 2, 8:39 am, Andreas Jung <[EMAIL PROTECTED]> wrote: > >> So why the hell is SA trying to insert something into my 'zielgruppen' > >> table? > > > any table in your SELECT statement for which its full set of primary > > key columns are represented in the columns clause of the SELECT, will > > generate an INSERT. > > What is the sense of this behavior? > > -aj > > application_pgp-signature_part > 1KHerunterladen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
