This repository has been archived by the owner on Sep 1, 2022. It is now read-only.
Reset to hasql-pool-0.8.0.2 upstream #5
Draft
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
Connections created before calling 'flush' won't be reused afterwards.
Since it better be local to the dev environment
Since it better be local to the dev environment
Somehow, we import GHC.Event.Windows.ConsoleEvent.Close on Windows via Hasql.Pool.Prelude, which conflicts with Close.
rename Close to avoid name ambiguity, fixing Windows build
Hm, I don't think anyone but us was using this repo. So I'd be fine with archiving as well. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This resets the fork to upstream, preserving the history. The rationale being that we shouldn't keep a diverging fork around if we're not using it since that's just confusing, but we also shouldn't lose the history since PostgREST main referenced this repo.
Alternatively, let's just archive this repository? Or would that cause trouble?