-
Hello, I have read in the documentation and saw in examples that namespaces should be prepared statically. Is that correct? I have tried to create new relationship tuples for non-existing namespace and (obviously) got an error. Should namespace creation / configuration be part of deploy procedure when new feature arrives given that this new feature introduces new namespace? Are there are any ways to create namespace in runtime, without configuration file modification? Or maybe any plans on it? If not, please explain why is it a bad idea. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
It says in the docs:
.
Maybe @zepatrik can answer this part 🙂 |
Beta Was this translation helpful? Give feedback.
-
We are currently evaluating whether we want to keep the current, table separated approach or distinguish namespaces by column. With the current approach, you can still add new namespaces with zero downtime, because the config files are hot-reloaded and migrations can be applied to a new namespace during operation (might slow down the database, but I have not tried it). I recommend you try it with a non-production environment beforehand. For sqlite in-memory there is an issue already to apply migrations on namespace config changes: #446 |
Beta Was this translation helpful? Give feedback.
-
Is there any updates on it? |
Beta Was this translation helpful? Give feedback.
It says in the docs:
.
Maybe @zepatrik can answer this part 🙂