Devart Forums

AndreyR

I recommend you to take a look at our Entity Framework Query Samples.
They describe how to use several storage models with one conceptual model.
Take a look at this blog article as well.
Hope these links describe the scenario you are interested in.

AndreyR

Thank you for the additional information, I have reproduced the issue.
We will let you know about the results of our investigation.

AndreyR

We have already considered the situation with Enumeration support in Entity Framework here in our blog.
There was an Enumeration support added in the Entity Framework 4.2 June 2011 CTP, but it supports only Enums of integer type, while in PostgreSQL Enums are of literal type.
Could you please specify what Enum type are you interested in?

AndreyR

Could you please specify the scenario you are planning to use ODBC in?
You are mentioning Entity Developer, so I suppose you are planning to use one of ORMs - Entity Framework, LinqConnect, or NHibernate. Could you please specify the ORM you are going to proceed with?

AndreyR

Plazmdk, does your function return a set of records? If so, please upgrade to the latest 5.30.185 build - we have fixed a similar error in it.
Please notify us if the error persists.

AndreyR

We have added the design time support for the Tinyint(1) as Boolean only in Devart Entity models (.edml) at the moment.
I recommend you to use Devart Entity models in your project instead of Microsoft Entity model. We have more control over the metadata in our models, and a more convenient designer - Entity Developer.

AndreyR

We don't provide this functionality at the moment.
If you are interested in it, you can add a suggestion on our Entity Developer User Voice.

AndreyR

There is a peculiarity in the handling of escape symbols in PostgreSQL, it differs from the SQL Standard a bit. First, you can turn on the standard_conforming_strings option on your server, in this case the

Code: Select all

var filteredSites = sites.Where(o => o.Host == "\").ToList();

query will work correctly.
Please note, that this PostgreSQL behaviour will probably be changed for SQL Standard compatibility.
However, this setting will not change the Like behaviour. It is associated with the fact that EF provider works in the disconnected mode, and it doesn't have an opportunity to know server settings before the generated query is executed.
So, we recommend you to use the parameters instead of the literals in your query, like in the following example:

Code: Select all

string literal = "\";
var filteredSites = sites.Where(o => o.Host.EndsWith(literal)).ToList(); 
var filteredSites = sites.Where(o => o.Host == literal).ToList();

AndreyR

We will post here when this functionality is implemented.
The investigation is in progress.

AndreyR

This feature is added in the latest 6.30.185 build of dotConnect for Oracle. The new build can be dowloaded from here (the trial version) or from Registered Users' Area (for users with active subscription only):
For the detailed information about the improvements and fixes available in dotConnect for Oracle 6.30.185, please refer to
this announcement.

AndreyR

This feature is added in the latest 4.0.15 build of Entity Developer for SQL Server. The new build can be dowloaded from here (the trial version) or from Registered Users' Area (for users with active subscription only):
For the detailed information about the improvements and fixes available in EntityDeveloper for SQL Server 4.0.15, please refer to
this announcement.

AndreyR

This problem is fixed in the latest 5.30.185 build of dotConnect for PostgreSQL. The new build can be dowloaded from here (the trial version) or from Registered Users' Area (for users with active subscription only):
For the detailed information about the improvements and fixes available in dotConnect for PostgreSQL 5.30.185, please refer to
this announcement.

AndreyR

The upcoming build already contains the fix for the Guid Identity problem.
I will let you know as soon as this build is released.

AndreyR

I recommend you to create a new C# or Visual Basic class library, add a new or existing Devart Entity model or Devart LinqConnect model, and then simply reference this assembly in your projects.
If you are interested in implementing some business logic over the generated code, I recommend you to take a look at this article, for example. It deals with Entity Framework, if you are interested in LinqConnect, take a look at this LINQ to SQL article, our LinqConnect is LINQ to SQL-compatible.

AndreyR

Could you please send us a test project illustrating the reported behaviour?
This is unexpected behaviour at the first sight.

Search found 2919 matches