https://github.com/davisdevelopment/hx-pmdb
pure-Haxe persistent data store
https://github.com/davisdevelopment/hx-pmdb
database embedded-database haxe javascript jit python
Last synced: about 2 hours ago
JSON representation
pure-Haxe persistent data store
- Host: GitHub
- URL: https://github.com/davisdevelopment/hx-pmdb
- Owner: DavisDevelopment
- License: gpl-3.0
- Created: 2018-08-15T21:25:42.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2020-04-11T17:48:57.000Z (about 5 years ago)
- Last Synced: 2025-04-19T06:56:53.398Z (11 days ago)
- Topics: database, embedded-database, haxe, javascript, jit, python
- Language: Haxe
- Homepage:
- Size: 906 KB
- Stars: 4
- Watchers: 3
- Forks: 3
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# hx-pmdb
### An Embedded DataStore Engine for the [Haxe](https://haxe.org/) Language
Written in pure Haxe code, PmDb aims at being a feature-rich and powerful embedded database to be used in any
Haxe project requiring persistent data management.
#### NOTE: Disregard following message. Updated README coming very soon
PmDb is still *very* much a Work-In-Progress, and should be ruled out entirely for any sort of production use (for now).
PmDb's implementation is quite experimental at the moment, and puts a lot of focus on the JavaScript/NodeJS target. That doesn't mean that it won't work on other targets, but the kind of performance that PmDb is designed to coax out of JavaScript should not be expected on any of the other targets (except maybe Flash?), and that's including the Java and C++ targets. It should still be fast enough for many use cases on those targets, but it will most likely be most useful in JavaScript-rich environments (specifically running on Google's V8 engine).
Lots of implementation details still up in the air, but the goal list so far is this:
- [ ] Allow declaration of a schema to improve performance some, without *requiring* one.
- [ ] When no schema is provided, gather type-information about the data being stored at runtime
- [ ] Represent queries as trees of nodes, much like an AST, but inextricable from (in fact, identical to) its ["interpreter"](https://en.wikipedia.org/wiki/Interpreter_(computing))
- [ ] Use hscript (or something similar) for writing out queries a Strings
- [ ] Support a fluent, Object-Oriented API for query building
- [ ] Design internal algorithms to take all reasonable measures for maximizing the degree to which V8 (& associated JIT optimizer) JIT-compile the Database-related portions of your application
##### Immediate Roadmap:
- [ ] Finish the prototype for the APIs surrounding query-creation and execution of UPDATE queries
- [ ]