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.
Context:
Support
FOR UPDATE Of tablename SKIP LOCKED
syntax:Going to look at adding FOR x OF [tables] syntax to the rest of the locking kinds hence making this a draft (Plus updating to use the (_ &: _) esqueleto style instead of an existential type
This allows a the
FOR UPDATE SKIP LOCKED
behaviour when you have aLEFT OUTER JOIN
with a nullable side. Currently you will get the error:The workaround currently using esqueleto is to do seperate queries and then join them manually if you want to select rows for an update while skipping locked rows (or to just do a raw query). I ran into this situation at work.
See: https://www.postgresql.org/docs/current/sql-select.html
namely:
also documented in MySQL:
https://dev.mysql.com/doc/refman/8.0/en/select.html
Usage example would be
@since
declarations to the Haddock.stylish-haskell
and otherwise adhered to the style guide.After submitting your PR: