Thanks!  That was it.  Adding db.commit() at the end made it work.

 

Best Regards,

 

Joel

>>> Jim Vickroy <Jim.Vickroy-32lpuo7BZBA@public.gmane.org> 7/17/2008 4:15 PM >>>

Joel Bard wrote:
> Hi-
>
> I'm connecting from linux x86_64 to a sqlserver2005 instance using mxODBC 3.0.1 with unixODBC.  I'm able to retrieve data with no problem.  When I try a simple insert:
>
>
>         c=db.cursor()
>         p1="test"
>         p2="mxodbc test"
>         c.execute("insert into bug" + \
>                   " (UIElement,Description)" + \
>                   "values (?,?)" \
>                   ,(p1,p2) \
>                   )
>
> c.rowcount is 1 but the row is not present in the table.  If I execute the same sql command using isql it works.  The table uses an autoincrement key column and values for the key are consumed even though the record is not being created.  c.messages is empty.  The same behavior is seen regardless of whether parameters are used and regardless of wether I use execute or executedirect.  Any help would be appreciated.
>
> Thanks,
>
> Joel
>
>
>
>
> _______________________________________________________________________
> eGenix.com User Mailing List                     http://www.egenix.com/
> https://www.egenix.com/mailman/listinfo/egenix-users
>  
Hi Joel,

Is this perhaps a transactional issue?  Have you tried to explicitly
commit the insert transaction?

-- jv

Disclaimer: I not an mx.ODBC user -- just a "lurker".