sector119 wrote:
>
> Oh, I forgot about that, it wasn't that behaviour that I realy
> axpect..
> I modify sql/compiller.py a bit to show what I mean. If I specify some
> bindparam'eters at value(...) I want _only_ that columns to be at
> update SET or insert VALUES..
>
> --- compiler.py.orig    2009-11-02 18:00:17.548954070 +0200
> +++ compiler.py 2009-11-02 18:01:11.682036402 +0200
> @@ -793,9 +793,9 @@
>
>          # if we have statement parameters - set defaults in the
>          # compiled params
> -        if self.column_keys is None:
> -            parameters = {}
> -        else:
> +        parameters = {}
> +
> +        if self.column_keys is not None and not stmt.parameters:
>              parameters = dict((sql._column_as_key(key), required)
>                                for key in self.column_keys if key not
> in bind_names)

unfortunately thats not the usage contract of an insert() statement. 
You'll have to pass the appropriate dictionary of parameters to execute(),
or pre-compile the `insert()` construct with the appropriate dialect.

--~--~---------~--~----~------------~-------~--~----~
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 
sqlalchemy+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to