[sqlalchemy] Re: Exclude Autogenerated Timestamp Column

2008-01-14 Thread Dean Halford
Good points - although restructuring the database around integer PKs is out of the question at the moment and we also need to support operations where 'road shoot' databases are merged into our master database... so we do have one legitimate use for GUIDs :) If I run across a way to fetch

[sqlalchemy] Re: Exclude Autogenerated Timestamp Column

2008-01-11 Thread Dean Halford
Thanks for the responses guys. The PassiveDefault() parameter did exactly what I wanted it to do - which was to exclude that column from the generated insert query so that MS SQL could handle those on it's own. ... now to figure out why I am getting an unsubscriptable object type error from the

[sqlalchemy] Re: Exclude Autogenerated Timestamp Column

2008-01-11 Thread Dean Halford
, shot.id, shot.now, shot.[rowNumber] FROM shot WHERE shot.id IS NULL - cheers On Jan 11, 1:46 pm, Michael Bayer [EMAIL PROTECTED] wrote: On Jan 11, 2008, at 4:37 PM, Dean Halford wrote: Thanks for the responses guys. The PassiveDefault

[sqlalchemy] Re: Exclude Autogenerated Timestamp Column

2008-01-11 Thread Dean Halford
, or trying to autoload the definition via table reflection? On Jan 11, 2008 5:23 PM, Dean Halford [EMAIL PROTECTED] wrote: thanks micheal - the only reason we went with 3.11 was the following statement on the wiki: Currently (Aug 2007) the 0.4 branch has a number of problems with MS- SQL