Page 1 of 1

ODAC 6.05.0.7: Minor issue with mixed case field as pk.

Posted: Thu 17 May 2007 14:54
by MarkF
Hi Folks!

I'm using the new build (I notice that it isn't announced above yet by the way) and have found a minor issue. If a table has a primary key field that needs to be quoted (i.e. "EmpNo") and ROWID is not used, then the primary key is not recognized and the refresh SQL falls back to using all fields instead of just the pk. Not a big deal, but it might be good to fix. Thanks for the new version!

-Mark Ford
Benthic Software

Posted: Fri 18 May 2007 07:40
by Plash
We could not reproduce the problem. Please send to odac*crlab*com a complete small sample that demonstrates the problem, including script to create server objects.

Posted: Fri 18 May 2007 19:37
by MarkF
Sorry! I made a mistake in the cause of the problem. It's not a mixed case pk fieldname, it's a mixed case tablename that causes the problem. You can see the problem by editing a table named "Test" that has a primary key. The actual bug is in the TOraDataSet.GetKeyList function. I think you can fix it just by removing the line:

TableName := AnsiUpperCase(TableName);

as the call to GetKeyList already normalizes the tablename.

I hope that helps!

-Mark

Posted: Mon 21 May 2007 08:22
by Plash
We have fixed this problem. The fix will be included in the next build of ODAC.