Devart Forums

AndreyR

We are investigating the possibility to add this functionality for Microsoft models as well. However, I'm unable to provide a definite timeframe for this functionality to be implemented.
Once again: our Devart Entity model generates the code that is fully compatible with the default Microsoft one (actually, it duplicates it in most cases, but we have added some additional features).

AndreyR

Are you using the Microsoft ADO.NET Entity Data model (.edmx)?
We have added the Tiny As Boolean support only for Devart Entity models (.edml). The functionality of the Devart Entity models is almost identical to the Microsoft Entity models, but our models are edited in the more convenient designer - Entity Developer, which is integrated in Visual Studio. To add a Devart Entity model to your project, go to Add New Item...->Data->Devart Entity model.

AndreyR

The new "raw guid as string" SSDL type will be added in the nearest build (this build will be released in a week or so).
This type is partially supported: Insert, Update, and Delete operations are supported. The Select queries with Where conditions containing this type like the

Code: Select all

context.RawTable.Where(rawTable => rawTable.RawColumn == "D3BC058453DC43CCB7C542D8345388FD")

or

Code: Select all

string value = "D3BC058453DC43CCB7C542D8345388FD";
context.RawTable.Where(rawTable => rawTable.RawColumn == value)

are supported as well.

However, we cannot guarantee the correct handling of the LINQ Extension methods like

Code: Select all

context.RawTable.Where(rawTable => rawTable.RawColumn.Contains("DC43CCB7C542"))

or

Code: Select all

context.RawTable.Where(rawTable => rawTable.RawColumn.IndexOf("DC43CCB7C542") > 0)

This functionality is almost implemented, however, we have some questions regarding implementation details:

1. Is the default ('N') format "00000000000000000000000000000000" appropriate? Guid.ToString() uses the "00000000-0000-0000-0000-000000000000" ('D') format as the default one, but it is longer for 4 symbols.
2. Do you need the possibility to select the string representation format (i.e. select which of the 'N', 'D', 'B', 'P', 'X' formats to use for the string representation)?
3. What should be the empty string literal representation? Namely, in the query like

Code: Select all

context.RawTable.Where(raw => raw.RawColumn == "")

the "" literal should be translated to null or to Guid.Empty("00000000-0000-0000-0000-000000000000")?
If you have any other propositions, please let us know.

AndreyR

The problem is fixed in the upcoming build. Follow the announcements on the forum.

AndreyR

We have changed the behaviour. Please note that the correct StoreGeneratedPattern setting for DateTime columns with the default value set to getdate() is Identity, because the Default value is taken into account only on Insert.

AndreyR

Thank you for the report. The problem is fixed, the fixed build will be available in a week or two.

AndreyR

The problem is fixed. Follow the announcements on our forum.

AndreyR

The CREATE DATABASE and Code First Fluent mapping does not support database-specific .functionality.
The only way of Code First usage I can recommend is to use the DbContext code generation template with the existing database.

AndreyR

We have fixed this problem as well. Follow the announcements at the forum.

AndreyR

You are correct in your assumption. However, there is a simple solution.
If you open the context connection explicitly, EF uses this connection instance for all DB operations during the entire context lifetime. So, add the following code after the context construction code:

Code: Select all

(context as IObjectContextAdapter).ObjectContext.Connection.Open();

AndreyR

I have successfully created a model from a partitioned Oracle table and succeeded in both querying it and modifying data using Entity Framework.
Please note that the Model First and Code First approaches are not possible with partitioned tables, and tables with partitioned indexes.

AndreyR

Thank you for the report, I have reproduced the issue. We are investigating it, I will let you about the results.

AndreyR

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

AndreyR

Thank you for the report, however, we are already aware of this problem.
The reason for the issue is the fact that PostgreSQL server does not provide built-in support for the "@" placeholder. We are investigating the possibility to add the support for this placeholder.

AndreyR

Please open the %Project Folder%\.Web\bin\Debug\.Web.dll assembly in any Resource Viewer (JetBrains dotPeek, for example), and verify that the paths to the .ssdl, .csdl, and .msl files are identical to the ones mentioned in web.config of the .Web application.
This error should not be associated with the materialized views.

Search found 2919 matches