You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@dbrakenhoff is working on storing a configuration file (json format) in the Pastastore. It would be a nice addition to store some metadata in this configuration file as well. Maybe formatted in a certain manner. This way people can store some information on the purpose of the PastaStore, what the (different) models represent etc. Would be nice to print this information when loading the PastaStore as well maybe?
The text was updated successfully, but these errors were encountered:
I propose a pstore.info attribute (ideally nicely formatted)? This can either be a new file in the database folder, or we can add it to the existing .pastastore file.
We could store this in the .pastastore file for databases that write to the local disk. For non-disk databases an info message should be written to the zip file if exported?
If we want to add it to the .pastastore file, one challenge to deal with is that currently this .pastastore file is overwritten at every initialize of a connector. So we'd have to find a way to persist this info message, or only update the relevant parts of .pastastore file on load. Maybe a separate readme info file makes more sense?
@dbrakenhoff is working on storing a configuration file (json format) in the Pastastore. It would be a nice addition to store some metadata in this configuration file as well. Maybe formatted in a certain manner. This way people can store some information on the purpose of the PastaStore, what the (different) models represent etc. Would be nice to print this information when loading the PastaStore as well maybe?
The text was updated successfully, but these errors were encountered: