feat: implement 'MERGE' statement builder (PostgreSQL 15+) #392
  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.
  
    
  
    
First of all, thank you for maintaining this cool project!
This PR introduces support for building
MERGEstatements, which were added to PostgreSQL starting from version 15. The new builder enables developers to constructMERGE INTO ... USING ... ON ... WHEN ...queries in the same fluent, composable style as other Squirrel statements (SELECT, INSERT, UPDATE, etc.).MERGEcombines the capabilities ofINSERT ... ON CONFLICT ... DO UPDATEand conditionalUPDATElogic in a single statement.It is especially useful for batch operations and upserts with complex matching conditions, reducing the need for multiple round trips to the database.
More about the
MERGEstatement: https://www.postgresql.org/docs/current/sql-merge.htmlExample usage: