Description
The DatabaseObjects library is .NET object relational mapping tool that contains a large set of powerful classes that interface to the underlying database system. Classes and properties in the business layer / model are marked with attributes (or functions overridden) in order to indicate the table and field mappings to the database. The library is simple, powerful and easy to learn. There are no external files to setup - everything is setup using standard object-oriented techniques. It is light-weight, flexible and provides facilities for ensuring maximum performance. It is also under active development and requests for changes are always welcome.
DatabaseObjects alternatives and similar packages
Based on the "ORM" category.
Alternatively, view DatabaseObjects alternatives based on common mentions on social networks and blogs.
-
TypeORM
Data-Mapper ORM for TypeScript and JavaScript (ES7, ES6, ES5). Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Server, Oracle, WebSQL databases. Works in Node.js and Browser. -
Entity Framework
Object-relational mapper that enables .NET developers to work with relational data using domain-specific objects -
FreeSql
FreeSql is the ORM in .NetCore, .NetFramework, And Xamarin. It supports Mysql, Postgresql, SqlServer, Oracle, Sqlite, Odbc, 达梦, And MsAccess. -
Fluent NHibernate
Fluent, XML-less, compile safe, automated, convention-based mappings for NHibernate. -
LINQ to DB
The fastest LINQ database access library offering a simple, light, fast, and type-safe layer between your POCO objects and your database. -
Dapper Extensions
Small library that complements Dapper by adding basic CRUD operations (Get, Insert, Update, Delete) for your POCOs -
Entity Framework 6
Object-relational mapper that enables .NET developers to work with relational data using domain-specific objects -
NPoco
Simple microORM that maps the results of a query onto a POCO object. Based on Schotime's branch of PetaPoco -
SmartSql
SmartSql = MyBatis + Cache(Memory | Redis)+ ZooKeeper + R / W Splitting + Dynamic Repository .... -
MicroOrm.Dapper.Repositories
Repository for CRUD operations -
SQLProvider
A general F# SQL database erasing type provider, supporting LINQ queries, schema exploration, individuals, CRUD operations and much more besides. -
MongoDB Repository pattern implementation
Repository abstraction layer on top of Official MongoDB C# driver -
DbExtensions
Data-access framework with a strong focus on query composition, granularity and code aesthetics. -
JsonFlatFileDataStore
Simple JSON flat file data store with support for typed and dynamic data. -
NReco.Data
Lightweight provider-independent DAL for .NET Core: abstract query, SQL command builder, CRUD operations, object mapping.. -
MongoFramework
An "Entity Framework"-like interface for MongoDB -
MicroLite ORM
MicroLite ORM is a micro Object Relational Mapper for the .NET framework. It is designed to be easy to use, extensible and testable. -
Linq.Expression.Optimizer
System.Linq.Expression expressions optimizer. -
EntityFramework.DatabaseMigrator
EntityFramework.DatabaseMigrator is a WinForms utility to help manage Entity Framework 6.0+ migrations. -
Excel2SqlServer
Library for importing Excel spreadsheets into SQL Server tables -
Entity Framework Core
Object-relational mapper that enables .NET developers to work with relational data using domain-specific objects -
LLBLGen Pro
Entity Modeling solution for Entity Framework, NHibernate, Linq to SQL and its own ORM framework: LLBLGen Pro Runtime Framework. [$][Free Lite version]
Pixel-Perfect Multi-Platform Applications with C# and XAML
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of DatabaseObjects or a related project?
README
DatabaseObjects
Database Support
- SQL Server
- MySQL
- SQLite
- HyperSQL
- Microsoft Access
- Pervasive
Environment Support
- Windows
- iOS via MonoTouch
- Android via MonoDroid
- OSX / Linux via Mono
Overview
The DatabaseObjects library is .NET object relational mapping tool that contains a large set of powerful classes that interface to the underlying database system. Classes and properties in the business layer / model are marked with attributes (or functions overridden) in order to indicate the table and field mappings to the database. The library is simple, powerful and easy to learn. There are no external files to setup - everything is setup using standard object-oriented techniques. It is light-weight, flexible and provides facilities for ensuring maximum performance. It is also under active development and requests for changes are always welcome.
License
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
SQL Support
The library also supports other database commands for creating / altering tables, indexes, views and specifying table joins, arithmetic expressions, aggregates, grouping, ordering, unions and support for all common data types and more. All commands are database agnostic.
Videos
A series of tutorial videos are available [here].(http://www.youtube.com/user/80twix/)
Documentation
All documentation and other information is available on the website www.hisystems.com.au/databaseobjects
Example
Below is a really simple example of what the library can do. This is really just a taste, see the demo project or the unit test project for more advanced examples.
namespace Northwind.Model
{
public class Northwind
{
public Suppliers Suppliers { get; private set; }
public Northwind()
{
var database = new DatabaseObjects.MicrosoftSQLServerDatabase("localhost", "Northwind");
this.Suppliers = new Suppliers(database);
}
}
[DatabaseObjects.Table("Suppliers")]
[DatabaseObjects.DistinctField("SupplierID", eAutomaticAssignment: DatabaseObjects.SQL.FieldValueAutoAssignmentType.AutoIncrement)]
[DatabaseObjects.OrderByField("CompanyName")]
public class Suppliers : DatabaseObjects.Generic.DatabaseObjectsEnumerable<Supplier>
{
internal Suppliers(DatabaseObjects.Database database)
: base(database)
{
}
}
public class Supplier : DatabaseObjects.DatabaseObject
{
[DatabaseObjects.FieldMapping("CompanyName")]
public string Name { get; set; }
[DatabaseObjects.FieldMapping("ContactName")]
public string ContactName { get; set; }
internal Supplier(Suppliers suppliers)
: base(suppliers)
{
}
}
}
namespace Northwind.Executable
{
using Model;
public class Program
{
public static void Main(string[] args)
{
var model = new Northwind();
foreach (Supplier supplier in model.Suppliers)
System.Console.WriteLine(supplier.Name);
}
}
}
Demo Project
The demonstration project is available in a separate repository on Github here. It includes a number of examples on how to utilise the library. To run the demo project in conjunction with the library it must be located in same directory as the library.
For example:
/DatabaseObjects /DatabaseObjects.Demo
Unit Test Project
The unit test project is available in a separate repository on Github here. It is also a good resource for examples on how to utilise the library. To run the unit tests project in conjunction with the library it must be located in the same directory as the library.
For example:
/DatabaseObjects /DatabaseObjects.UnitTests
*Note that all licence references and agreements mentioned in the DatabaseObjects README section above
are relevant to that project's source code only.