48 results found
-
EF Core support for MySQL Json data type
Add support for MySQL Json data type fields in the EF Core (LINQ, manipulate data)
2 votes -
Support Multiple Framework Targeting
When generating content we are forced to pick the framework version. If we are creating a common business object library we may need to target multiple frameworks. The class generation is not affected, but the data context can be wrapped in #IF to indicate the framework we are compiling for.
1 vote -
json
Expand PgSqlJsonbFunctions to include JSON Processing Functions to allow for direct manipulation of Json data on the server.
1 vote -
Publish .Net5 compatible preview version of Devart.Data.Oracle.EFCore
In order to test migration to .Net5
We need to have at least a preview version of Devart.Data.Oracle.EFCore compatible with .Net51 vote -
Entity Framework support in SQL Server
Entity Framework translates binary code to SQL query text then SQL Server has to parse this text, compile and execute.
Why Entity Framework and SQL Server can't comunicate directly using a binary protocol?3 votes -
Entity developer model explorer improvement
Visual Studio 2017 and .Net Core project.
Model explorer nodes collapse every time you navigate to another document and go back to Entity Developer designer. To reproduce the issue:
- Open an .efml file
- Make sure database model explorer is visible.
- Expand any nodes (Methods, Complex Types, etc.)
- Open another document (let's say some C# code)
- Go back to Entity Developer.
- Observe that all nodes are collapsed.
This issue results in less productivity and frustration when you need to go back and forth between code and DB model.
1 vote -
Support Dependency class in Entity Framework by default
It would be nice feature, if you would implement the Dependency Classes (MySQLDependency, SQLDependency, OracleDependency…)
directly into your Entity Framework with the T4 Code Template Generation.3 votes -
Index instead of foreign key constraints.
A global option to insert indexes rather than foreign keys should be an option. There are many of us that do not use foreign keys for reasons of updating databases and performance while indexes used instead actually improve performance with the model able to maintain the association.
This is a low hanging fruit guys and will improve everyone's performance of the models. Please consider.
This is should be a universal option for all frameworks.
3 votes -
Support for the upcoming version of EF6 cross platform and .net Core 3.0
Support for the upcoming version of EF6 cross platform and .net Core 3.0
According to the roadmap, EF6 will be released as compatible with .net Core 3.0 with the ability to run on linux (source: https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-3-and-support -for-windows-desktop-applications /)EF6 work on .NET Core is currently tracked on the following GitHub issues:
– https://github.com/aspnet/EntityFramework6/issues/189 – Support PackageReference
– https://github.com/aspnet/EntityFramework6/issues/231 – Support for new csproj format
– https://github.com/aspnet/EntityFramework6/issues/271 – Support for .NET Core3 votes -
Spatial support for EFCore, compatible with other providers.
With EFCore 2.2 there will be Spatial support via NTS for SQLite, SqlServer in-memory and postgress via a standardized interface. Devart should implement something similar for their drivers.
9 votes -
Support EF7
Add support for the new EF7.
We need to test it before the actual release date.43 votes -
OracleJsonFunctions.Value should generate returning clause
Oracle's JSONVALUE function supports a stynax like JSONVALUE(Column,"$.path.to.property" RETURNING data_type [number,date,timestamp])
OracleJsonFunctions.Value function should cover this functionality and allow developers can write queieries like below
context.Entities.Where(t=> OracleJsonFunctions.Value(t.Json,"$.SomeScalarValue")> 1);Adding "Error on Erro"r or "null on error" syntax generation would also be nice.
JSON_VALUE function details :
https://docs.oracle.com/database/121/SQLRF/functions093.htm#SQLRF566683 votes -
EF should allow defining query for entity selection but should not require CRUD stored procedure
Right now entity framework requires CRUD stored procedure if you define select query for the entity. This should be optional only. EF provider should construct DML queries based on TableName property of the entity. For more details see Devart #236214.
1 vote -
6 votes
-
Enable with Code First Comments from Code to DB
Auto-insert code xml-documenten (c#) to Database comments (Oracle).
Example:/// <summary>
/// Id for XYZ
/// </summary>
public int Id {get;set}should auto create the follwoing sql:
comment on column mytabel.id is 'Id for XYZ';
3 votes -
Provide Nuget Package that supports Entity Framework Core
The dotconnect for Oracle nuget package does not support Entity Framework Core. I have to buy the Professional or Developer versions to get that functionality. The problem with that is that we cannot install software in our secured environment without a lengthy request/assessment process. Also, we really don't need all that functionality; we just need support for EF Core. Please release a version of the nuget package with Entity Framework Core support.
1 vote -
Unite into Batch Inserts for entities with columns having the StoreGeneratedPattern attribute value set to Identity or Computed (Oracle)
Hello,
I see that batch for "Statements with the RETURNING clause, for example, statements that update or insert entities with columns having the StoreGeneratedPattern attribute value set to Identity or Computed." is not supported.
The code generated for such an insert is for this sample table is:
DECLARE
updatedRowid ROWID;
BEGIN
INSERT INTO ACTIONAR(CNP, NUME, PRENUME, TIP, REZIDENTA)
VALUES (:p0, :p1, :p2, :p3, :p4)
RETURNING ROWID INTO updatedRowid;
OPEN :outParameter FOR SELECT ID FROM ACTIONAR WHERE ROWID = updatedRowid;
END;The SQL for batched inserts could look like this:
DECLARE
updatedRowid1 ROWID;--First in batch
updatedRowid2 ROWID;--Second in batch
BEGIN
INSERT…30 votes -
Unique Constraints in the Entity Framework
The Microsoft EF team is currently designing unique constraint support in EF. See http://blogs.msdn.com/b/efdesign/archive/2011/03/09/unique-constraints-in-the-entity-framework.aspx. Vote for this to make sure this is also supported by DevArt's provider.
144 votes -
PostgreSql - Option to insert empty string values as NULL
With PostgreSql, there is a difference between an empty string value (represented as '') and a NULL value.
With Oracle and SQL-Server, an empty string is always inserted as NULL.
So, if there is a unique constraint on a column and the application insert a empty string, the constraint will be violated for the second insertion.
It would be nice to have an option to insert empty string values as NULL for dotConnect for PostgreSQL, to have the same behavior than Oracle or SQL-Server, and not specifically avoid empty strings in the application to work with PostgreSQL...
12 votes -
ID generators
Capability to assign an ID generator (for example, Sequence, Guid, Increment, or Hi-Lo) to a Primary Key column.
21 votes
- Don't see your idea?