|
dotConnect for Oracle, formerly known as OraDirect .NET, is an enhanced ORM enabled data provider for Oracle that builds on ADO.NET technology to present a complete solution for developing Oracle-based database applications. It introduces new approaches for designing application architecture, boosts productivity, and facilitates the development of database applications.
Fast and Advanced ADO.NET Provider
dotConnect for Oracle offers both high performance native connectivity to the Oracle database and a number of innovative development tools and technologies. It supports a wide range of Oracle-specific features, such as Advanced Queuing, Alerts, Pipes, Direct Path Loading, Change notifications, Transparent Application Failover, REF cursors, objects, packages, and others.
RAD Approach
dotConnect for Oracle provides a vast number of GUI tools that increase your productivity. It integrates into Visual Studio Server Explorer and other tools, and provides advanced visual component editors to simplify component tweaking. DataSet tools, such as DataSet Wizard, DataSet Editor, DataSet Manager, provide you an easy way to create and edit typed and untyped DataSets.
ORM Solutions
dotConnect for Oracle offers enhanced ORM support with a bundled visual designer for ORM models - Entity Developer. dotConnect for Oracle supports ADO.NET Entity Framework, NHibernate, and LinqConnect (formerly known as LINQ to Oracle) - our own ORM solution, closely compatible to Microsoft LINQ to SQL, while extending its functionality with its own features.
dotConnect for Oracle Editions
dotConnect for Oracle is available in five editions: Developer, Professional, Standard, Mobile, and Express.
- The Standard Edition represents a fully-featured ADO.NET data provider with design time support and advanced classes.
- The Professional Edition adds more classes, tools, technologies, and integration capabilities.
- The Developer Edition combines the whole featureset with including dbForge Fusion for Oracle Standard Edition, an advanced add-in for designing databases and easily managing data and schema objects from your IDE.
The Mobile Edition is equivalent to the Standard Edition for .NET Compact Framework.
LinqConnect (formerly known as LINQ to Oracle)
- The possibility to use .IsRowVersion() method for properties with non-binary data types when using the fluent mapping approach is added
- The Parent property is added to the IInheritanceConfiguration interface
Entity Developer
- The support for materialized views is implemented
- The Use ObservableCollection property of the DbContext template is implemented (Entity Framework models)
- The behaviour is changed: now the 1:1 and 1:0..1 associations are displayed differently on the diagram
(LinqConnect models)
Entity Framework
- The overloads for Contains and Matches methods are added to the OracleTextFunctions class for using full-text search with the binary columns
- The config.QueryOptions.TrueValueNumber configuration option is added to specify SQL generation for True values (either equal to 1 or not equal to 0)
The spatial constant functionality is implemented
What's new in version 9.12.1064
- The bug with blocking thread during retrieving a connection from the pool, when connections from the same pool are used in several threads, is fixed
- The bug with memory leak when running a lot of queries in the OCI mode is fixed
Entity Developer
- The new attribute DisplayName is implemented for model objects' extended properties which are available via template properties
- The new options --ContextNamespace and --DefaultNamespace are added to the Create-Model command of Console Entity Developer
- The new extended model property Base Context Type is added for specifying a parent class for the generated context in EF Core Model
- The new extended properties Base Type for complex types and Base Complex Type for model are implemented in EF Core Model
- The %type name% keyword is supported in the Base Type extended property of entities and complex types, and in Base Complex Type, Base Entity Type, Base Context Type extended model properties for setting generic base type in EF Core Model
- Code generation is improved: RelationalIndexBuilderExtensions.HasDatabaseName is generated now instead of RelationalIndexBuilderExtensions.HasName in EF Core 5
- Display names of extended properties in EF Core Model are updated: Entity Base is renamed to Base Type in class properties, Entity Base is renamed to Base Entity Type in model properties, Context Base is renamed to Base Context Type in model properties
- The bug with setting additional keyboard mapping scheme via menu Options on Windows with German display language is fixed
LinqConnect (formerly known as LINQ to Oracle)
- The new property Local is added to the Table and Table classes to return a collection of the entities attached to the context
- The new method GetEntityState(object entity) is added to Table class and ITable interface to return one of the EntityState values
- The bug with throwing "Bad key member '...' in association '...' of type '...'." in runtime by .NET Standard compliant assemblies is fixed
Entity Framework support
- Entity Framework Core 5.0.2 is supported
- Entity Framework Core 3.1.11 is supported
- The new metadata to describe autoincremental columns via annotations in EF Core Code-First Migrations are implemented
- The new config.DatabaseScript.Index.UseCurrentSchema option (default value is false) is added for ability to ignore schema set for indexes via EF Core Code-First Migrations
- The behavior is changed: config.DatabaseScript.Index.UseCurrentSchema is set to false by default; as a result, the schema argument in CreateIndex(), DropIndex(), AddUniqueConstraint(), DropUniqueConstraint() operations is now applied not only to the table name, but also to the index name, i.e. previously, the index was always created in the current schema, and now it is created in the schema of the table to which the index belongs
- The bug with ignoring schema set for indexes via CreateIndex(), DropIndex(), AddUniqueConstraint(), DropUniqueConstraint() operations of EF Core Code-First Migrations is fixed
|
