task/WG-377: drop deprecated ObservableDataProject table #232
Conversation
This file contains 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 reverts commit 74977c7.
PostGIS manages its own schema
The default behavior for spatial indexing in GeoAlchemy2. This migration should have been added earlier in projects development
rstijerina
approved these changes
Dec 11, 2024
Base automatically changed from
task/WG-396-sqlachemy-postgis-follow-on
to
main
December 11, 2024 19:44
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.
Overview:
This PR drops the deprecated ObservableDataProject table. It was kept to ensure everything went right after #216 was deployed.
Related Jira tickets: