[ ] config value for setting the output/input directory for these... fixtures I guess?
[ ] web UI for dumping and loading data from file
Considerations
Adding unique handles to all records will make this workable across databases without having to codify the database ID
as an intrinsic model attribute (e.g. we can let it just be an implementation detail of the application). In many cases,
this can be the name of the record, or the slug, in the case of KitLine and SourceMaterial. Ideally, it aligns with
the easiest way for a human to consider and communicate about the record as well.
In theory, it should be easy for users to modify their tables in, for example, JSON, while the app is "offline", and
have that cleanly translate to model records. For example, if I were to add a Kit via JSON
Assumption: non-persistent database (e.g. disposable SQLite databases).
Requirements:
Considerations
Adding unique handles to all records will make this workable across databases without having to codify the database ID as an intrinsic model attribute (e.g. we can let it just be an implementation detail of the application). In many cases, this can be the name of the record, or the slug, in the case of
KitLine
andSourceMaterial
. Ideally, it aligns with the easiest way for a human to consider and communicate about the record as well.In theory, it should be easy for users to modify their tables in, for example, JSON, while the app is "offline", and have that cleanly translate to model records. For example, if I were to add a Kit via JSON
I should be able to expect that to be equivalent to running up the console and entering something like