Allow usage of different schemas for documents #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds support for using dedicated schemas for storing documents. This way one can separate storage of documents of different scopes do dedicated schemas per scope. THis allows for a better structuring of the documents within the database. This commit does **not** handle creating the schemas. The schema needs to be available to the DocumentStore for this to work. Basically this allows one to set the schema right within the table-name by separating schema and tablename by a dot like this: `schemaname.tablename`. The name will then be split on the dot and the former part be used as schema-name, the later part as table-name. Any table-prefixes will only be added to the table name, not to the scheme.
This adds the schema-enabling to all queries that target the tablename.
This commit adds the creation of the schema to the process of creating the document store. So now the schema does not need to be already available when the document store is created
codeliner
approved these changes
Sep 9, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds support for using dedicated schemas for storing
documents. This way one can separate storage of documents of different
scopes do dedicated schemas per scope. THis allows for a better
structuring of the documents within the database.
This commit does not handle creating the schemas. The schema needs
to be available to the DocumentStore for this to work.
Basically this allows one to set the schema right within the table-name
by separating schema and tablename by a dot like this:
schemaname.tablename. The name will then be split on the dot and theformer part be used as schema-name, the later part as table-name. Any
table-prefixes will only be added to the table name, not to the scheme.