Devart Forums

Could you please specify the version of the Entity Developer and Visual Studio you are using?
Is the problematic model created in a previous version of Entity Developer? If so, could you please send us the model, we will investigate the situation.

I have sent a sample project to the e-mail address that you provided in your forum profile.
Please either change the project or create a new one to reproduce the problem.
Update. Unfortunately, the e-mail was not delivered. Could you please provide an alternative e-mail?

Thank you for the report, I have reproduced the problem.
I will let you know about the results of our investigation.

Is the problem resolved with using PgSqlEntityProviderServices?
We are working on the improvement of the UnpreparedExecute connection string parameter.

Thank you for the report, I have reproduced the issue.
I will let you know as soon as it is fixed.

Dynamic Linq does not support our extensions.
We are investigating the possibility of adding the case-insensitive Like implementation.

Thank you for the inquiry. I have reproduced this situation. It is associated with the fact that this column is not marked as Identity in the database.
We will investigate the possibility of changing this behaviour for Guids.
I will let you know about the results of our investigation.

We plan to add support for the BINARY_FLOAT and BINARY_DOUBLE data types in the Direct mode in future versions. Unfortunately, I don't have a definite timeframe for this functionality to be implemented.
We will investigate the possibility to perform a default mapping to Single/Double, respectively.
I will let you know about the results of our investigation.

Could you please specify the classes you have created an inheritance between?
If possible, please send us the model and describe some steps to reproduce the issue.

Could you please send us the model you are using, and the LINQ to Entities (or Entity SQL, if you are using it) that result in the error?

Could you please try increasing the connection timeout in the model connection string?
This can be done by adding "ConnectionTimeout=30;" to the model connection string.
If 30 seconds is not enough, you can try to set it to 0, this value means that no timeout exception should be raised.
Please let us know about the results of changing ConnectionTimeout .

I'm unable to reproduce the issue using the ReadOnly attribute in both Entity Developer 3.50.128 and 3.50.132.
Is your model under any source control?

The issue is associated with the fact that Code First uses a different approach to create a command, and our functionality did not cover this use case.
The workaround I have already suggested allows for these peculiarities.

You can change the type of the BINARY_FLOAT property to "single" in SSDL, and to "System.Single" in CSDL part of the model.
As for the BINARY_DOUBLE property, the mappings should be "double" and "System.Double", respectively.
I have checked this approach, it worked for me.
If you are using a Devart Entity model, the Store properties can be edited in Model Explorer->Tables/Views->[Your table]->Columns.
If you are using Microsoft Entity models, you should open the model in XML Editor and make changes in it.

Yes. the null values in database will be returned as null values for nullable DateTime properties.