Devart Forums

StanislavK

We couldn't reproduce the issue: when the command execution fails, we get server errors (e.g., 'ORA-12571: TNS:packet writer failure') instead of access violation in our environment, and the command is disposed successfully after catching this exception.

I've sent you a sample project, please try performing the scenario you described with it, and tell us if the issue occurs. If it does not, please specify what should be changed in the test project to reproduce the problem, or send us your sample.

StanislavK

We have fixed the CreateDatabase issue, the fix is available in the latest 3.70.311 build of dotConnect for SQLite. The new build can be downloaded from
http://www.devart.com/dotconnect/sqlite/download.html
(the trial version) or from Registered Users' Area (for users with active subscription only).

For more information about the fixes and improvements available in dotConnect for SQLite 3.70.311, please refer to
http://www.devart.com/forums/viewtopic.php?t=23472

StanislavK

We have fixed this issue, the fix is available in the latest 3.1.43 build of LinqConnect. The new build can be downloaded from
http://www.devart.com/linqconnect/download.html
(the trial version) or from Registered Users' Area (for users with active subscription only).

For more information about the fixes and improvements available in LinqConnect 3.1.43, please refer to
http://www.devart.com/forums/viewtopic.php?t=23468

StanislavK

The issues with the LINQ to SQL generator and updating identity fields are fixed in the latest 4.2.138 build of Entity Developer. The new build can be downloaded from
http://www.devart.com/entitydeveloper/download.html
(the trial and free versions) or from Registered Users' Area (for users with active subscription only).

For more information about the fixes and improvements available in Entity Developer 4.2.138, please refer to
http://www.devart.com/forums/viewtopic.php?t=23476

StanislavK

The fix for this issue is available in the new 3.1.43 build of LinqConnect. The new build can be downloaded from
http://www.devart.com/linqconnect/download.html
(the trial version) or from Registered Users' Area (for users with active subscription only).

For more information about the fixes and improvements available in LinqConnect 3.1.43, please refer to
http://www.devart.com/forums/viewtopic.php?t=23468

StanislavK

We have implemented the possibility of connecting as a user with a Unicode name in the Direct mode. This change is available in the latest 6.70.311 build of dotConnect for Oracle. The new build can be downloaded from
http://www.devart.com/dotconnect/oracle/download.html
(the trial version) or from Registered Users' Area (for users with active subscription only).

For the detailed information about the fixes and improvements available in dotConnect for Oracle 6.70.311, please refer to
http://www.devart.com/forums/viewtopic.php?t=23469

StanislavK

This behaviour is changed: if the HexBlob property is set to true, BINARY columns are dumped in the hexadecimal format as well. This change is available in the latest 6.70.311 build of dotConnect for MySQL. The new build can be downloaded from
http://www.devart.com/dotconnect/mysql/download.html
(the trial version) or from Registered Users' Area (for users with active subscription only).

For the detailed information about the fixes and improvements available in the new build, please refer to
http://www.devart.com/forums/viewtopic.php?t=23470

StanislavK

The problem described in this topic was caused by an error in compiling queries that included calls to stored procedures. More precisely, such compiled queries were holding a reference to the context instance. This issue was fixed in the 3.1.25 version of LinqConnect.

Apparently, the issue you are observing has another origin. Thank you for the sample project, we will investigating it and inform you about the results as soon as possible.

StanislavK

Sorry for the delay. Since the problem cannot be reproduced with the table from the sample, but occurs in the actual application, it (the problem) may be connected with a peculiarity of this actual table or the data stored in it. Could you please specify the script of this table and some test data, so that we are able to analyze the situation in more details?

If the table description should not be disclosed, you can, e.g., rename the table/column names to something abstract, like 'table1', 'column1' etc.

StanislavK

Please check the initial value of myComment.COMMENTS and the one set by 'e.NewValues["COMMENTS"].ToString()'. A probable reason for this situation is that these values are identical; in this case, the LinqConnect runtime will register no changes in this entity, thus no update command will be executed.

If these values are different, but still no update command is executed, please try simplifying the scenario: e.g., shorten it to just fetching the entity, modifying its COMMENTS property and submitting the changes:

Code: Select all

RTPCRDataContext context = Utilities.GetContext(); 
RTPCR_DAT myComment = context.RTPCR_DATs.First(
  d => d.EU_ID == {set the entity key here}
);
myComment.COMMENTS = {set the string constant here};
context.SubmitChanges();

Please tell us if the issue can be reproduced in this case.

StanislavK

At the moment, the installation package does not integrate LinqConnect into Visual Studio 2011.

As for the runtime, we did not perform complete testing of LinqConnect compatibility with .NET Framework 4.5, though simple tests run successfully.

We will post here when full support for Visual Studio 2011 and .NET Framework 4.5 is available.

StanislavK

Could you please specify the following:
- whether you are working with a LinqConnect or LINQ to SQL model;
- the version of LinqConnect (or Entity Developer) you are using;
- the exact way you are serializing entity objects.
If possible, please send us a small sample with which the problem can be reproduced.

For example, Entity Developer should not set a DataMember attribute on the Order.Customer navigation property by default, thus there should be no loops in the serialized Customer objects.

StanislavK

Thank you for the report, we have reproduced the issue. We will analyze it and inform you about the results as soon as possible.

StanislavK

The reason why DBMS-specific code is generated is that the attribute mapping mode is used by default. As multiple mapping attributes of the same type cannot be set for a single class/property, the attribute mapping can only be used for a single database.

To make your model database-ignorant, you can use the file mapping mode instead (you can change the mapping mode in the Model Settings dialog). In this case, the mapping metadata will be saved to a [YourModel].xml file. To work with different databases, you can do the following:
- generate several mapping files (e.g., one per DBMS);
- create the mapping source object from a particular mapping file;
- pass this object to your DataContext constructor.

Feel free to contact us if anything is unclear.

StanislavK

Sorry for the delay. Could you please describe how exactly you are inserting these rows? For example, please specify the following:
- whether you call the SubmitChanges method once or multiple times;
- whether you are using batch inserts (and if yes, what is the max batch size?);
- an approximate connection string you are using.
If possible, please specify the definitions of the tables you are working with and/or send us a small test project, so that we are able to analyze the situation in more details.

For some general tips on improving the LinqConnect performance, please refer to the corresponding article in our documentation:
http://www.devart.com/linqconnect/docs/Performance.html

Search found 1710 matches