Search Results for "entity framework"

Entity Framework 6 (EF6) is a proven object-relational (O/RM) mapper for .NET with many years of feature development and stabilization. Like O/RM, EF6 reduces the impedance mismatch between the relational and object-oriented worlds, allowing developers to write applications that interact with data stored in relational databases with strongly typed .NET objects that represent the domain of the database. application, and eliminate the need for much of the data access "mechanical" code that you would normally write. ...

...It allows you to interact with PostgreSQL via the most widely-used .NET O/RM from Microsoft, and use familiar LINQ syntax to express queries. It's built on top of Npgsql. The provider looks and feels just like any other Entity Framework Core provider. Aside from providing general EF Core support for PostgreSQL, the provider also exposes some PostgreSQL-specific capabilities, allowing you to query JSON, array or range columns, as well as many other advanced features. For more information, see the the Npgsql site.

Npgsql is an open source ADO.NET Data Provider for PostgreSQL, it allows programs written in C#, Visual Basic, F# to access the PostgreSQL database server. It is implemented in 100% C# code, is free and is open source. An Entity Framework Core provider is also available and exposes some features unique to the PostgreSQL database to EF Core users. Finally, a legacy Entity Framework 6.x (non-Core) provider is also available but is no longer being actively maintained. Npgsql is the open source .NET data provider for PostgreSQL. It allows you to connect and interact with PostgreSQL server using .NET.

...TypeORM supports both Active Record and Data Mapper patterns, unlike all other JavaScript ORMs currently in existence, which means you can write high-quality, loosely coupled, scalable, maintainable applications the most productive way. TypeORM is highly influenced by other ORMs, such as Hibernate, Doctrine and Entity Framework. Supports both DataMapper and ActiveRecord (your choice). Uni-directional, bi-directional and self-referenced relations.

Fluent Migrator is a migration framework for .NET much like Ruby on Rails Migrations. Migrations are a structured way to alter your database schema and are an alternative to creating lots of sql scripts that have to be run manually by every developer involved. Migrations solve the problem of evolving a database schema for multiple databases (for example, the developer's local database, the test database and the production database). Database schema changes are described in classes written in...

...Spring Data builds on Spring Framework, check the spring.io web-site for a wealth of reference documentation. If you are just starting out with Spring, try one of the guides.

...Architecturally it is one step above micro-ORMs like Dapper, Massive, or PetaPoco, in that you work with LINQ expressions, not with magic strings, while maintaining a thin abstraction layer between your code and the database. Your queries are checked by the C# compiler and allow for easy refactoring. However, it's not as heavy as LINQ to SQL or Entity Framework. There is no change-tracking, so you have to manage that yourself, but on the positive side you get more control and faster access to your data. In other words LINQ to DB is type-safe SQL. Alternatively, you can implement custom settings provider with ILinqToDBSettings interface. You can generate POCO classes from your database using T4 templates.

JPA framework to create persistent entity management programs. Intensive introspection based.

This framework allows the definition of attributes, entities and relations as used in entity-relationship (ER) models. It will then handle input and representation of data appropriately.

AutoSQL provides a simple and easy to use framework meant to be a substitute for J2EE Entity beans and JDO. AutoSQL data objects give just the right abstraction from a writing SQL without being too far removed from the power of SQL.