Skip to content
This repository has been archived by the owner on Feb 9, 2020. It is now read-only.

High level persistence proposal #35

Open
rogersm opened this issue Apr 11, 2018 · 0 comments
Open

High level persistence proposal #35

rogersm opened this issue Apr 11, 2018 · 0 comments
Assignees
Labels
enhancement New feature or request
Projects

Comments

@rogersm
Copy link
Contributor

rogersm commented Apr 11, 2018

  1. Use sqlite3 to store: world data (map, users & objects) and state.
  2. Have a minimal persistence memory to sqlite3 time.
  3. Have a highly coupled memory data model to sqlite3 (persist at struct member/variable at database field type)
  4. Because (2 & 3) we expect the programmer to have some SQL knowledge.
  5. Minimal set of objects to be persisted: Room, Thing, Exits, Tags (a kind of trait that can be attached to anything), Player, Non Player.
  6. Define a set of functions per object (4) to persist/update/retrieve from/to the database.
  7. Create a versioning system of database schema so it can be upgraded without user action.
@rogersm rogersm added the enhancement New feature or request label Apr 11, 2018
This was referenced Apr 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
Persistence
Awaiting triage
Development

No branches or pull requests

3 participants