Replies: 1 comment
-
It would be also really cool to switch them:
And we also need some kind of Upgrade instructions (EVENTS) to manage the data while an definition upgrade is made:
Or maybe/also something like this:
Layer updates should be performed in an transaction and if failed they will automatically rollback. Imagine you have thousands of namespaces and all databases need to be in sync, you will have no chance without such a system, or am i wrong? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It would be nice to see a new type of DEFINE LAYER to manage defaults for any kind of definition, e.g. when creating a namespace, database, table or field. In simplicity i was looking for something like this:
When upgrading the layer emailAddress with a new version the defined field will not change but can be updated manually:
Or using auto upgrade mechanism by default:
Another main idea is to create defaults for namespaces like automatically create or upgrade databases/tables and so on:
Is somthing planned or on the todo-list of this great project?
Beta Was this translation helpful? Give feedback.
All reactions