This repository has been archived by the owner on Jan 3, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 12
Using DeveelDB
tsutomi edited this page Dec 7, 2012
·
2 revisions
DeveelDB is by nature an embeddable SQL database system, designed to be consumed directly from .NET applications, referencing the kernel library (deveeldb.dll). This method gives provides the application a full-featured SQL-99 database management system, without establishing any network connection (not even locally). Managing and consuming databases will be done programmatically from within the application, without losing the concepts of transactions, nor all others features of a relational database system (constraints, triggers, etc.)
Advantages of this approach versus a network instance are the following:
- No network connection required
- Reduced security issues
- Performances speedup
- Compact footprint (application + data)
- Consistency of the solution
- Application can be shipped with data (read-only)
- Direct access to data
The disadvantages deriving form the use of such approach:
- Only one application at a time can access a database
- t can be consumed only by .NET/Mono applications
Please refer to this guide to learn how to use DeveelDB within your application
- Getting Started
- Basic Principles
- Operative Contexts
- Transactions
- Database Objects
- Data Types
- SQL Execution Plan
- SQL Model
- DeveelDB SQL Dialect
- Data Types
- Routines (Functions and Procedures)
- Collaborate
- Kernel Development
- External Contributions
- Bug Reporting
- Documentation