Concurrency exception when calling a teradata storedproc

G

Guest

Hi
I have a C# app that uses a dataadapter to update a table in a teradata
datawarhouse. It performs an update using a teradata stored procedure. In
teradata, stored procs dont actually return the number of rows updated but
instead return a 0 if successful. This results in a concurrency exception
being raised when the update is performed. Is there anyway to get around this
issue.

Regards
Syed
 
G

Guest

I have managed to get it to work. i used an output parameter in teradata
which results in the row count set to 1 and thus doesnot cause a concurrency
exception.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Concurrency via SqlCommand.ExecuteNonQuery 2
Optimistic Concurrency - DataRow.Column Error Property Not Set 1
vb.net data adapters - concurrency and insert comands 3
Concurrency Exception and Enforce Contraints problem 1
Concurrency issue on Update 4
DataSet concurrency exception (code inside) 6
StoredProc commits results in QueryAnalyzer but not in ADO.NET 4
DBConcurrencyException Not Thrown For INSERT Command 1

Top