When using concurency checks, rows affected returns -1

When using concurency checks, rows affected returns -1

Postby Goransi » Thu 06 Nov 2014 09:19

We've added db generated fields to our model to enable concurency checking. Our insert|update|delete queries are no longer simple but end with selecting db generated values.

Code: Select all
UPDATE SOME_TABLE
SET TABLE_ID = :p1,...
WHERE TABLE_ID = :key1 AND ((:nullchk1 = 1 AND LAST_UPDATE IS NULL) OR (LAST_UPDATE = :chk1)) RETURNING LAST_UPDATE INTO :ret1


Rows affected information is always -1. Is this by design or will this be fixed in the future versions? If so can we get any eta?

This is important to us as our product runs on different db servers. SQL version has no problem returning the correct rows affected info. This info is used to check if concurency violation has occured!
Goransi
 
Posts: 10
Joined: Thu 23 Jan 2014 22:48

Re: When using concurency checks, rows affected returns -1

Postby MariiaI » Fri 07 Nov 2014 11:15

Please specify the following details:
- the version of LinqConnect;
- the DDL/DML scripts for the necessary database tables;
- the definitions of the DataContext, entity classes (e.g., the model you are working with);

If possible, send us the test project, so that we are able to investigate the issue in more details and find the solution for you in a shortest time.
MariiaI
Devart Team
 
Posts: 1472
Joined: Mon 13 Feb 2012 08:17


Return to dotConnect for Oracle