When launching from devcontainer, unique DB indexes seem to be missing that enforce folder names within a space to be unique.
The expected behaviour is this validation message:
There doesn't seem to be any backend validation for uniqueness. This seems to work purely by adding the unique index. Probably in the libtest DB someone did this manually? The indexes are not in this migration script anyway but not sure if that is still supposed to be used.
The actual behavior is duplicate folder names (within the same space) being allowed.
Also space names are also not enforced uniquely. In the libtest environment trying to create a non-unique space results in an internal server error. In local devcontainer setup, this just works:
When launching from devcontainer, unique DB indexes seem to be missing that enforce folder names within a space to be unique.
The expected behaviour is this validation message:
There doesn't seem to be any backend validation for uniqueness. This seems to work purely by adding the unique index. Probably in the libtest DB someone did this manually? The indexes are not in this migration script anyway but not sure if that is still supposed to be used.
The actual behavior is duplicate folder names (within the same space) being allowed.
Also space names are also not enforced uniquely. In the libtest environment trying to create a non-unique space results in an internal server error. In local devcontainer setup, this just works: