Devart is glad to announce the release of the new versions of dotConnect ADO.NET data providers. New versions of Devart products offer significant improvements for Entity Framework Core and make debugging process easier by adding more configuration options to dbMonitor class.
Spatial Data Support for EF Core
dotConnect providers for MySQL, Oracle, PostgreSQL, and SQLite can now work with Spatial data in Entity Framework Core. This functionality is implemented in the new Devart.Data.<provider>.Entity.EFCore.NetTopologySuite.dll assembly, available for Full .NET Framework via the product installer, and for .NET Standard project — as a separate NuGet package. For SQLite this support is provided via the SpatiaLite SQLite extension.
Entity Developer also supports mapping spatial properties to database columns of corresponding types. When generating a model from a database, having spatial columns, it automatically downloads all the necessary NuGet packages to your projects.
Read more about our spatial data support in a separate blog article.
Full Text Search and Database-specific Functions Support for EF Core
Classes for using database-specific functions in LINQ to Entities that were previously supported for Entity Framework v4 – v6, are now supported for Entity Framework Core. These are the following classes:
Additionally, dotConnect providers now support full-text search for Entity Framework Core via the following classes:
All dotConnect providers allow monitoring their work via the free dbMonitor application and their descendants of DbMonitor class. It allows per-component tracing of database events such as commit, rollback, SQL statement execute, creating and destroying components, connection pooling events, etc.
The new version allows tweaking monitoring in more details and significantly decrease performance loss from monitoring. Now you can turn off costly call stack sending for all database events via the SendCallStack property of the DbMonitor class. Additionally, you can specify events that you want to monitor in the Filter property, and other events won’t be monitored.
And a bonus feature – now the DbMonitor class sends timestamps for database events with milliseconds included.