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

Remove --schema-name option #314

Closed
rustprooflabs opened this issue Apr 20, 2023 · 0 comments · Fixed by #316
Closed

Remove --schema-name option #314

rustprooflabs opened this issue Apr 20, 2023 · 0 comments · Fixed by #316
Labels
breaking Breaking change Technical Debt Not broken, not new, but not right either!
Milestone

Comments

@rustprooflabs
Copy link
Owner

Details

The concept of changing schema name from osm conflicts with many of the features in PgOSM Flex. The --schema-name option will be removed. Users that want to rename the schema (I'm one of them) can manually ALTER SCHEMA as necessary. That makes the disconnect an obvious choice removed from PgOSM Flex, along with the expectation that "everything will just work." (It won't)

For my use cases where I rename the schema, having PgOSM Flex do that for me adds no value/time savings/etc.

I hope this isn't a negative impact to anyone. I've been thinking about this for a while and still think this is the right choice in the long run. Leaving this in as inviting someone to encounter a bad time with some unexpected disconnect/bug.

@rustprooflabs rustprooflabs added Technical Debt Not broken, not new, but not right either! breaking Breaking change labels Apr 20, 2023
@rustprooflabs rustprooflabs added this to the 0.8.0 milestone Apr 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Breaking change Technical Debt Not broken, not new, but not right either!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant