P
PeterZ
To all you Oracle gurus out there,
I'm updating an Oracle table with an OleDbDataAdapter (win forms).
I'm using a timestamp column rather than comparing all the values to
determine concurrency violation. The way I set the timestamp column is
within the actual dataAdapter update/insert statement.
SYS_TIMESTAMP = SYSDATE ..... equivalent of Now() in SQL I believe?
Screenshot of update query builder:
http://www.insightgis.com.au/web/stuff/update_qry_builder.gif
This works fine, when an update is posted to the db it will write the
current SYSDATE to the timestamp column. However, the currently
displayed record on my form doesn't know about the new timestamp value,
therefore if you make a subsequent edit to that same record and try to
post changes to the db you get a concurrency violation error.
Question is, when the dataAdapter makes the update to the db, can it
refresh the local copy of the timestamp with the new value? Or do I
have to fish out the whole record from the db again? One of my tables
has 160 fields, so I'd rather not have to fish the whole record out
again for obvious reasons
How do you Oracle people get around this problem?
Cheers,
PeterZ
I'm updating an Oracle table with an OleDbDataAdapter (win forms).
I'm using a timestamp column rather than comparing all the values to
determine concurrency violation. The way I set the timestamp column is
within the actual dataAdapter update/insert statement.
SYS_TIMESTAMP = SYSDATE ..... equivalent of Now() in SQL I believe?
Screenshot of update query builder:
http://www.insightgis.com.au/web/stuff/update_qry_builder.gif
This works fine, when an update is posted to the db it will write the
current SYSDATE to the timestamp column. However, the currently
displayed record on my form doesn't know about the new timestamp value,
therefore if you make a subsequent edit to that same record and try to
post changes to the db you get a concurrency violation error.
Question is, when the dataAdapter makes the update to the db, can it
refresh the local copy of the timestamp with the new value? Or do I
have to fish out the whole record from the db again? One of my tables
has 160 fields, so I'd rather not have to fish the whole record out
again for obvious reasons
How do you Oracle people get around this problem?
Cheers,
PeterZ