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

Initial breaking changes #2

Merged
merged 2 commits into from
Oct 15, 2024
Merged

Initial breaking changes #2

merged 2 commits into from
Oct 15, 2024

Conversation

str4d
Copy link
Collaborator

@str4d str4d commented Oct 15, 2024

These are necessary changes vs schemer that I didn't do in #1 to keep schemerz 0.1.0 intentionally compatible with the latest version of schemer, but that need to be done going forward.

@str4d str4d mentioned this pull request Oct 15, 2024
@str4d str4d force-pushed the initial-breaking-changes branch from 2326fdf to a2552d0 Compare October 15, 2024 08:02
- **IMPORTANT BREAKING CHANGE**: `schemerz_postgres::PostgresAdapter::new` now
uses a default table name of `_schemerz` when the `table_name` argument is
`None`. If you were not setting this argument before and are migrating from
`schemer`, you will need to set `table_name` to `Some("_schemer".into())`.
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We were the only public dependent on schemer, so I think this notice should be all we need to do. But an alternative would be to remove the default and require the caller to always specify the table name.

Copy link
Contributor

@nuttycom nuttycom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK a2552d0

@nuttycom nuttycom merged commit 668f1ae into main Oct 15, 2024
8 checks passed
@nuttycom nuttycom deleted the initial-breaking-changes branch October 15, 2024 19:07
Copy link

@daira daira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Post-hoc ACK

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.

3 participants