Collation issue after upgrading to 7.6

[trumbjd1]

Hi All,

I just upgraded from dotConnect for Oracle 7.2 to 7.6. It works just fine until I try and update my EF model from the database (this is a DB First project). It insists that every single column in my model needs to be updated. The reason given for the change is:

Collation(old='',new='') was changed.

If I accept these changes, it clears out all the renamed fields and all my modified field mappings. The painful part is that it keeps doing the same thing every time I update the model which is killing me.

I am seeing the problem with EF 4 and 5 dll's.

Any ideas? Collation is an SQL Server term for the language setting I believe. Not sure why this is coming up...

--Jonathan

My connection string and other details.

User Id=XXXXX;Password=XXXXXX;Server=XXXXX;Direct=True;Sid=XXXXX;Port=1521;Pooling=true;Max Pool Size=7;Unicode=true;Connection Timeout=10

My language settings in Oracle:
AMERICAN_AMERICA.AL32UTF8

Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
Devart dotConnect for Oracle 7.6.192.0
Devart Entity Developer 5.0.56.0
Microsoft Visual Studio Ultimate 2012 Version 11.0.51106.01 Update 1
Microsoft .NET Framework Version 4.5.50709

[Shalex]

Thank you for your report. The bug with detecting changes in the Collation attribute of the column in SSDL by Update Model From Database wizard is fixed. We will post here when the corresponding build of dotConnect for Oracle is available for download.

[trumbjd1]

Wow, that was fast. I eagerly await the fix, thanks!

--Jonathan

[Shalex]

New build of dotConnect for Oracle 7.6.202 is available!
It can be downloaded from http://www.devart.com/dotconnect/oracle/download.html (trial version) or from Registered Users' Area (for users with active subscription only).
For more information, please refer to http://forums.devart.com/viewtopic.php?f=1&t=26199.

[trumbjd1]

Issue is indeed resolved!