Skip to content

Revert back to commit 01dcc24 #89

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

Merged
merged 1 commit into from
Feb 25, 2025
Merged

Conversation

CDThomas
Copy link
Contributor

This change reverts this repo back to 01dcc24.

The changes reverted include commits from:

We mostly want to revert the changes in #86 (since they aren't working as intended with Proxy), but #87 is also included since it's more recent (and also includes some ORE-related changes that would be tedious to untangle).

Since there aren't many changes after #86, the most pragmatic option is to revert to the last known-good state and redo the install/uninstall changes by hand on top of that.

Commands used to revert:

git reset --hard 01dcc247e4c2b527a78d3ed5277e1464141beca2
git reset --soft ed460fc653604207210e7cc6029e1292441d3bbb

This change doesn't use git revert because there were > 20 commits to revert and merge commits also don't play well with git revert.

This change reverts this repo back to 01dcc24.

The changes reverted include commits from:
- #86
- #87

We mostly want to revert the changes in #86 (since they aren't
working as intended with Proxy), but #87 is also included since it's
more recent (and also includes some ORE-related changes that
would be tedious to untangle).

Since there aren't many changes after #86, the most pragmatic
option is to revert to the last known-good state and redo the
install/uninstall changes by hand on top of that.

Commands used to revert:
```
git reset --hard 01dcc24
git reset --soft ed460fc
```

This change doesn't use `git revert` because there were > 20 commits
to revert and merge commits also don't play well with `git revert`.
@CDThomas
Copy link
Contributor Author

CDThomas commented Feb 25, 2025

Next steps after this PR:

  • Raise another PR in this repo to use the new format for ORE indexes from Proxy (JSON array of hex-encoded strings), but decode into the composite type used for ORE in PG. Test Proxy against the change to verify that ORDER BY and comparison operators work as expected.
  • Raise another PR to redo the work in Use same drop setup on install and uninstall #87

@CDThomas CDThomas marked this pull request as ready for review February 25, 2025 00:28
@CDThomas CDThomas merged commit ab9afc1 into main Feb 25, 2025
4 checks passed
@CDThomas CDThomas deleted the revert-ore-order-by-changes branch February 25, 2025 04:09
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