Skip to content

Switching schemas ad-hoc via Advanced.Options.DatabaseSchemaName #618

Description

@shanomacadaemia

Hello,

We are trying to switch schemas using the property above so that we can save documents for different clients under different schemas, much as RavenDB would allow you to specify a database name when opening a documentsession; however, this seems to only work about half of the time. I'm imagining that this is not the best solution as we are setting the schema at the DocumentStore level rather than at the Session level (which would likely affect all other open sessions). Is there any existing means of executing this or an analogue of this functionality currently?

My other idea is to lazily load a collection of document stores per client and inject them into the services dynamically.

Any assistance would be greatly appreciated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions