Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release v3.11.0 #108

Merged
merged 1 commit into from
Nov 8, 2023
Merged

Release v3.11.0 #108

merged 1 commit into from
Nov 8, 2023

Conversation

HeyNonster
Copy link
Contributor

  • Property tables can now live on a separate database to their parent models. This is achieved, on a per-model basis, by configuring the connection class that will be used by property sets. e.g. set self.property_sets_connection_class = Foo on the model to instruct property_sets to use Foo's database connection when looking for the property sets tables.

* Property tables can now live on a separate database to their parent models. This is achieved, on a per-model basis, by configuring the connection class that will be used by property sets. e.g. set `self.property_sets_connection_class = Foo` on the model to instruct `property_sets` to use `Foo`'s database connection when looking for the property sets tables.
@HeyNonster HeyNonster marked this pull request as ready for review November 8, 2023 10:21
@HeyNonster HeyNonster requested a review from a team as a code owner November 8, 2023 10:21
@HeyNonster HeyNonster requested a review from a team November 8, 2023 10:21
@HeyNonster HeyNonster merged commit 9219201 into master Nov 8, 2023
21 checks passed
@HeyNonster HeyNonster deleted the nony--release-v-3-11-0 branch November 8, 2023 10:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants