On Aug 23, 2007, at 11:18 AM, che wrote:

>
> Hi,
>
> On 23 Авг, 17:47, Michael Bayer <[EMAIL PROTECTED]> wrote:
>> dont compile() the insert statement yourself here; since you are only
>> executing it once, theres nothing to be gained by manually compiling
>> first.
> this was the minimal code demonstrating the issue.
> i planned to do this many times for bulk insert into the table in
> database-independent way.
>
>>  Its also the source of the error. the issue is that when the
>> Insert is compiled with no "values" clause, it produces column
>> entries for all three columns; but youre only sending two columns in
>> your argument list.  this behavior is the same in 0.3.
>
> seems there is some other prob too:
> - in 0.3 it is issued 2 statements:
> select nextval('"Manager_id_seq"')
> and then:
> INSERT INTO "Manager" (duties, name, id) VALUES (%(duties)s, %(name)s,
> %(id)s)
> with the ids got from the db and the other parameters.
>
> - in 0.4 it is issued only the last insert with all ids None which
> leads to the error
>

i cant reply to this issue for another week since im out of town.  as  
a workaround, placing "autoincrement=False" on your primary key  
column for now may resolve the issue.





--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to