eXtremeDB Embedded Database Specification
|
eXtremeDB 32-bit Specifications |
eXtremeDB 64-bit Specifications |
|
|
|
|
Maximum object per database: 2,147,483,647 |
Maximum database size: 18.446 exabytes (quintillion) |
|
Maximum classes per database: 32,767 |
Maximum classes per database: 65,535 |
|
Maximum indexes per database: 32,767 |
Maximum indexes per database: 65,535 |
|
Maximum fields or vectors per class: 32,767 |
Maximum fields or vectors per class: 65,535 |
|
Maximum fields per index: 32,767 |
Maximum fields per index: 65,535 |
|
Maximum elements per vector: 32,767 |
Maximum elements per vector: 65,535 |
|
Memory requirements: As little as 50K |
Memory requirements: As little as 50K |
|
Maximum databases open simultaneously: 16 |
Maximum databases open simultaneously: 16 |
|
Maximum simultaneous connections per database: 64 |
Maximum simultaneous connections per database: 64 |
Operating Systems Supported
- Linux, QNX Neutrino, LynxOS, uC/OS-II
- Nucleus, INTEGRITY, eCos, uCLinux
- Windows Embedded Platforms
- VxWorks, Quatros RTXC
- Solaris, HP-UX, Windows 98/Me/NT/2000/XP/Vista
- eXtremeDB source code for all platforms; eXtremeDB can also run without an operating system (bare bones board)
Programming interfaces
- A library of standard database functions (e.g. cursor functions) provides an interface common to all applications using the eXtremeDB real-time database
- An application-specific native API is generated when a database schema is compiled. Because it is based on a developer’s data design, this interface is intuitive and optimized for a project’s exact needs.
- SQL and ODBC API (eXtremeSQL)
Index types and queries
- eXtremeDB supports virtually all data types, including structures, arrays, vectors and BLOBs and Unicode
- Querying methods include hash indexes for exact match searches, R-trees for GIS/mapping applications
- B-tree indexes support queries for pattern match, range retrieval and sorting
- Also supported: KD-trees for multidimensional data, and Patricia tries (useful for prefix searches such as IP and telecom routing)
- 'Voluntary' indexes enable program control over population of index
- Object-identifier references provide direct data access
- Autoid supports system-defined object identifiers
- Rather than storing duplicate data, indexes contain only a reference to data, keeping memory requirements to an absolute minimum
- Object history is provided optionally
Supported data types
- 1, 2, 4, 8-byte signed/unsigned integers
- float, double
- date, time
- Char (fixed length)
- String (variable length)
- Fixed-size array
- Variable-length vector
- Structs (embedded to any depth)
- BLOB
- Autoid (auto-increment)
- User-defined object-id and references
- Unicode
Debugging environment
- The eXtremeDB debug-mode run-time includes numerous traps in the database code, for detection and easy remediation of programming errors
- The eXtremeDB-generated programming interface exploits the type-checking features of the compiler, with programmer mistakes generating a compile-time error
- The eXtremeDB in-memory database is available with source code, for complete control of the development environment
Development environments
- gnu toolchain (gcc 2.96 and higher)
- Tornado 2.0 and 2.2 (GNU and Diab compilers)
- QNX Momentics IDE (C, C++, Embedded C++)
- Metrowerks CodeWarrior IDE (various platforms)
- GreenHills Multi
- Microsoft Visual Studio (C/C++, .NET)
eXtremeDB editions
- eXtremeDB Standard Edition (in-memory embedded database)
- eXtremeDB Fusion (hybrid in-memory and on-disk storage)
- eXtremeDB High Availability
- eXtremeDB Transaction Logging
- eXtremeDB-64 (64-bit)
- eXtremeDB Kernel Mode
- eXtremeSQL SQL interface
- eXtremeWS embedded Web server
Learn More From Embedded Database