Elenesski's Object DB
Elenesski
$38.50
(no ratings)
|
Date |
Price |
|---|---|
|
日時 |
価格($) |
|
03/19(2018) |
38.5 |
|
11/27(2024) |
38.5 |
Jump AssetStore
Elenesski's Object Database (EODB) v2.x is a platform for persisting and loading multiple objects of any format to/from an in-memory database and then, as a separate operation, save the database to disk. It provides data layer so that you can implement the feature of "save game" / "load game" in your game by providing an in-memory database you read/write from, then save to disk with a single call.
Detailed Documentation and Examples
Support Forum
Elenesski Games Link
Version 2.0 Changes:
* Support for Fowler's Identity Map pattern so that there is only one instance of an object in memory at a time.
* Support for Foreign Keys to make parent-child relationships possible and faster searching as well.
* Changes to support NEODB (the network extension for EODB).
* Minor bug fix.
Main Features:
* Support multiple open databases at the same time.
* Does not use any DLL's and full source is provided, enabling an easy implementation on mobile devices. Further, this allows databases to be shared between platforms such as PC/mobile without having to deal with complex data, database, database version compatibility issues.
* Uses a headerless binary format to store your object's attributes. This produces highly compact and tamper resistant databases.
* Supports 27 primitive types (plus their array equivalent) with an extensible data framework that is resilient to updates in the EODB release.
* Supports an unlimited flexible dictionary based indexing system for simplified and efficient searching. Further, indexes can be conditionally appended to (or deleted from) and values can be derived from your object instead of indexing only existing attributes.
* It provides an easy way of storing your object's data in a binary format and dynamically defining how to read attribute values, lists, dictionaries and other types without needing to predefine a schema.
* Save a single object with a predefined identifier or multiple objects of the same type can be stored within the same database and multiple databases can be open at the same time. Multiple objects can then be found using the class name or an index.
* Provides a way to handle different versions so that objects stored in your player's databases can be loaded even as your newer game versions store newer formats of the same object.
* It does not use serialization and and natively does not use SQL or tables, so you don't need to do ORMs or break arrays, dictionaries, lists or other composite objects down in order to store them.
PDF Documentation is included in the package but for the most up-to-date version of the documentation, see our website documentation (link above).
