You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like some API changes causeing compile error.
Configuring beam-mysql-0.1.0.0...
Preprocessing library for beam-mysql-0.1.0.0..
Building library for beam-mysql-0.1.0.0..
[2 of 4] Compiling Database.Beam.MySQL.Syntax ( Database/Beam/MySQL/Syntax.hs, .stack-work/dist/x86_64-linux-nopie/Cabal-2.2.0.1/build/Database/Beam/MySQL/Syntax.o )
.stack-work/downloaded/j6hLIMXda_k-/beam-mysql-1c267d7b612ceb5cf2305a5050e0f2a68b3f281b/Database/Beam/MySQL/Syntax.hs:149:7: error:
• Couldn't match expected type ‘Maybe
(Sql92DeleteExpressionSyntax MysqlDeleteSyntax)
-> MysqlDeleteSyntax’
with actual type ‘MysqlDeleteSyntax’
• In the expression:
MysqlDeleteSyntax
$ emit "DELETE FROM "
<>
mysqlIdentifier tbl
<>
maybe
mempty
(\ where' -> emit " WHERE " <> fromMysqlExpression where')
where_
In an equation for ‘deleteStmt’:
deleteStmt tbl where_
= MysqlDeleteSyntax
$ emit "DELETE FROM "
<>
mysqlIdentifier tbl
<>
maybe
mempty
(\ where' -> emit " WHERE " <> fromMysqlExpression where')
where_
In the instance declaration for
‘IsSql92DeleteSyntax MysqlDeleteSyntax’
|
149 | MysqlDeleteSyntax $
| ^^^^^^^^^^^^^^^^^^^...
.stack-work/downloaded/j6hLIMXda_k-/beam-mysql-1c267d7b612ceb5cf2305a5050e0f2a68b3f281b/Database/Beam/MySQL/Syntax.hs:151:78: error:
• Couldn't match type ‘Text’ with ‘MysqlExpressionSyntax’
Expected type: Maybe MysqlExpressionSyntax
Actual type: Maybe Text
• In the third argument of ‘maybe’, namely ‘where_’
In the second argument of ‘(<>)’, namely
‘maybe
mempty
(\ where' -> emit " WHERE " <> fromMysqlExpression where')
where_’
In the second argument of ‘(<>)’, namely
‘mysqlIdentifier tbl
<>
maybe
mempty
(\ where' -> emit " WHERE " <> fromMysqlExpression where')
where_’
|
151 | maybe mempty (\where' -> emit " WHERE " <> fromMysqlExpression where') where_
| ^^^^^^
The text was updated successfully, but these errors were encountered:
Looks like some API changes causeing compile error.
The text was updated successfully, but these errors were encountered: