We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Function deleteBy is broken in cases where at least one of the fields of composite unique key is nullable.
deleteBy
The text was updated successfully, but these errors were encountered:
Hm, that's not good. Can you describe the behavior you observe?
Sorry, something went wrong.
Here is an example:
deleteDir :: BotId -> Maybe DirId -> Integer -> ReaderT SqlBackend IO () deleteDir botId mParId idx = -- -- NOTE : esqueleto query always works, but vanilla persistent -- query is not working in cases where mParId == Nothing, -- probably null /= null sql problems here... -- -- P.deleteBy $ UniqueDir botId mParId idx -- delete . from $ \dir -> where_ $ ( dir ^: DirBotId ==. val botId ) &&. ( dir ^: DirParentId & case mParId of Nothing -> isNothing Just parId -> (==. val (Just parId)) ) &&. ( dir ^: DirIdx ==. val idx )
No branches or pull requests
Function
deleteBy
is broken in cases where at least one of the fields of composite unique key is nullable.The text was updated successfully, but these errors were encountered: