Migrate data to document-driven database format

[atoff]

Look to migrate existing data structure to a mongo-db type JSON format, to remove issues with current format not being a traditional database style

[A-Lawrence]

https://github.com/calebporzio/sushi

😉

[atoff]

Good shout - I remember a certain Axon showing me this earlier. Thinking in the long term though, would be nice to give each variant a UUID to ensure easy merges into outdated / custom data sets (whilst still being able to maintain collaborative git version control)

[A-Lawrence]

It's not my package, but does that not mean you wouldn't be able to use it as a relation in a database at risk of it changing, if you aren't just going to give them all ids manually?

If you don't care about that, why don't you hook into the boot::creating event and set the Id as the md5 of the data?

[atoff]

Trying to keep the package framework agnostic - this repo is just about data. But if I updated, say, the A320 neo variant, at the moment there would be no easy way to merge the new data into an existing import (say an SQL table). You could probably form a unique relationship based on ICAO code and variant and model, but if each variant had a database-like ID this would be a very easy update operation.

What I am kind of aiming for is a way of essentially maintaining a document-driven database, such that people can create, update and delete variants on GitHub without having to resort to a web-based editor (for example https://ourairports.com/), where it is easy to maintain a UUID in the form of an auto-increment ID in the table (If that makes sense)

MD5'ing the row could work, but I think it would be nice to provide a method to update the data for a variant without having to create a new entry in the table (although yes, in theory, the data for a aircraft variant should never change)

Open to ideas!