20 messages in com.googlegroups.sqlalchemy[sqlalchemy] Re: save_or_update and c...
FromSent OnAttachments
Smoke09 Dec 2007 11:54 
Michael Bayer09 Dec 2007 12:36 
Smoke09 Dec 2007 14:26 
Michael Bayer09 Dec 2007 18:11.py
Smoke10 Dec 2007 00:39 
Rick Morrison10 Dec 2007 09:46 
Michael Bayer10 Dec 2007 10:36 
Rick Morrison10 Dec 2007 10:57 
Smoke10 Dec 2007 13:48 
Rick Morrison10 Dec 2007 15:20 
Paul Johnston10 Dec 2007 15:43 
Smoke12 Dec 2007 05:30 
Rick Morrison12 Dec 2007 08:54 
Smoke12 Dec 2007 13:56 
Smoke18 Dec 2007 15:40 
Smoke18 Dec 2007 15:43 
Michael Bayer18 Dec 2007 16:03 
Rick Morrison18 Dec 2007 16:37.py
Smoke19 Dec 2007 01:52 
Rick Morrison19 Dec 2007 06:42 
Subject:[sqlalchemy] Re: save_or_update and composit Primary Keys... MSSQL / pyodbc issue ?
From:Michael Bayer (mike@zzzcomputing.com)
Date:12/18/2007 04:03:56 PM
List:com.googlegroups.sqlalchemy

On Dec 18, 2007, at 6:44 PM, Smoke wrote:

Sorry because i'm a bit late ( work deadlines are struggling my time! :) ). I've made some different configurations and schema definitions... and i've noticed that it never updates a row if i set the datetime field as PK ( never! even if i set it as the only PK .. ). If i set composite PKs excluding any datetime column everything works fine ( it also works if i set a datetime as PK at the database side and excluding it at the schema on sqlalchemy side.. ). Sorry about the mess with the PKs between the former examples but i was only trying to say that changing the schema results that everything works fine...

if i set "start" and "identifier" as primary key columns, script works fine for both sqlite and postgres, using both 0.4.1 and trunk. mssql guys will have to try it on mssql.