mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-18 13:02:11 +03:00
342391f39d
This upgrades the version of Ormolu required by the HGE repository to v0.5.0.1, and reformats all code accordingly. Ormolu v0.5 reformats code that uses infix operators. This is mostly useful, adding newlines and indentation to make it clear which operators are applied first, but in some cases, it's unpleasant. To make this easier on the eyes, I had to do the following: * Add a few fixity declarations (search for `infix`) * Add parentheses to make precedence clear, allowing Ormolu to keep everything on one line * Rename `relevantEq` to `(==~)` in #6651 and set it to `infix 4` * Add a few _.ormolu_ files (thanks to @hallettj for helping me get started), mostly for Autodocodec operators that don't have explicit fixity declarations In general, I think these changes are quite reasonable. They mostly affect indentation. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/6675 GitOrigin-RevId: cd47d87f1d089fb0bc9dcbbe7798dbceedcd7d83
113 lines
3.5 KiB
Haskell
113 lines
3.5 KiB
Haskell
-- | Postgres Translate Insert
|
|
--
|
|
-- Translates IR inserts to Postgres-specific SQL INSERT statements.
|
|
module Hasura.Backends.Postgres.Translate.Insert
|
|
( mkInsertCTE,
|
|
toSQLConflict,
|
|
insertCheckConstraint,
|
|
insertOrUpdateCheckExpr,
|
|
)
|
|
where
|
|
|
|
import Hasura.Backends.Postgres.SQL.DML qualified as S
|
|
import Hasura.Backends.Postgres.SQL.Types
|
|
import Hasura.Backends.Postgres.Translate.BoolExp
|
|
import Hasura.Backends.Postgres.Translate.Returning
|
|
import Hasura.Prelude
|
|
import Hasura.RQL.IR.Insert
|
|
import Hasura.RQL.Types.Backend
|
|
import Hasura.SQL.Backend
|
|
|
|
mkInsertCTE ::
|
|
Backend ('Postgres pgKind) =>
|
|
InsertQueryP1 ('Postgres pgKind) ->
|
|
S.TopLevelCTE
|
|
mkInsertCTE (InsertQueryP1 tn cols vals conflict (insCheck, updCheck) _ _) =
|
|
S.CTEInsert insert
|
|
where
|
|
tupVals = S.ValuesExp $ map S.TupleExp vals
|
|
insert =
|
|
S.SQLInsert tn cols tupVals (toSQLConflict tn <$> conflict)
|
|
. Just
|
|
. S.RetExp
|
|
$ [ S.selectStar,
|
|
insertOrUpdateCheckExpr
|
|
tn
|
|
conflict
|
|
(toSQLBool insCheck)
|
|
(fmap toSQLBool updCheck)
|
|
]
|
|
toSQLBool = toSQLBoolExp $ S.QualTable tn
|
|
|
|
toSQLConflict ::
|
|
Backend ('Postgres pgKind) =>
|
|
QualifiedTable ->
|
|
OnConflictClause ('Postgres pgKind) S.SQLExp ->
|
|
S.SQLConflict
|
|
toSQLConflict tableName = \case
|
|
OCCDoNothing ct -> S.DoNothing $ toSQLCT <$> ct
|
|
OCCUpdate OnConflictClauseData {..} ->
|
|
S.Update
|
|
(toSQLCT cp1udConflictTarget)
|
|
(S.buildUpsertSetExp cp1udAffectedColumns cp1udValues)
|
|
$ Just
|
|
$ S.WhereFrag
|
|
$ toSQLBoolExp (S.QualTable tableName) cp1udFilter
|
|
where
|
|
toSQLCT ct = case ct of
|
|
CTColumn pgCols -> S.SQLColumn pgCols
|
|
CTConstraint cn -> S.SQLConstraint cn
|
|
|
|
-- | Annotates the check constraint expression with @boolean@
|
|
-- (<check-condition>)::boolean
|
|
insertCheckConstraint :: S.BoolExp -> S.SQLExp
|
|
insertCheckConstraint boolExp =
|
|
S.SETyAnn (S.SEBool boolExp) S.boolTypeAnn
|
|
|
|
-- | When inserting data, we might need to also enforce the update
|
|
-- check condition, because we might fall back to an update via an
|
|
-- @ON CONFLICT@ clause.
|
|
--
|
|
-- We generate something which looks like
|
|
--
|
|
-- > INSERT INTO
|
|
-- > ...
|
|
-- > ON CONFLICT DO UPDATE SET
|
|
-- > ...
|
|
-- > RETURNING
|
|
-- > *,
|
|
-- > CASE WHEN xmax = 0
|
|
-- > THEN {insert_cond}
|
|
-- > ELSE {update_cond}
|
|
-- > END
|
|
-- > AS "check__constraint"
|
|
--
|
|
-- See @https://stackoverflow.com/q/34762732@ for more information on the use of
|
|
-- the @xmax@ system column.
|
|
insertOrUpdateCheckExpr ::
|
|
QualifiedTable ->
|
|
Maybe (OnConflictClause ('Postgres pgKind) S.SQLExp) ->
|
|
S.BoolExp ->
|
|
Maybe S.BoolExp ->
|
|
S.Extractor
|
|
insertOrUpdateCheckExpr qt (Just _conflict) insCheck (Just updCheck) =
|
|
asCheckErrorExtractor $
|
|
S.SECond
|
|
( S.BECompare
|
|
S.SEQ
|
|
(S.SEQIdentifier (S.QIdentifier (S.mkQual qt) (Identifier "xmax")))
|
|
(S.SEUnsafe "0")
|
|
)
|
|
(insertCheckConstraint insCheck)
|
|
(insertCheckConstraint updCheck)
|
|
insertOrUpdateCheckExpr _ _ insCheck _ =
|
|
-- If we won't generate an ON CONFLICT clause, there is no point
|
|
-- in testing xmax. In particular, views don't provide the xmax
|
|
-- system column, but we don't provide ON CONFLICT for views,
|
|
-- even if they are auto-updatable, so we can fortunately avoid
|
|
-- having to test the non-existent xmax value.
|
|
--
|
|
-- Alternatively, if there is no update check constraint, we should
|
|
-- use the insert check constraint, for backwards compatibility.
|
|
asCheckErrorExtractor $ insertCheckConstraint insCheck
|