[[ 🏗 =br6Go Vervis ]] :: [📥 Inbox] [📤 Outbox] [🐤 Followers] [🤝 Collaborators] [🐛 Tickets] [📖 Wiki] [✏ Edit]

Created on 2019-05-06 by ~fr33domlover

[🐤 Followers] [⤴ Dependencies] [⤷ Dependants] [✋ Claim requests] [✏ Edit]

I noticed that forge.angeley.es has errors about unique constraints. I tested and discovered that the persistent-parser library produces wrong results! It succeeds to parse, but all the unique constraints have only 1 parameter, picking the 1st one and ignoring the rest. Possibly there are more problems, inconsistencies between forge and dev due to forge migrations being done with this parser from the start.

dev has problems too. In less tables, but, all tables created with the parser need fixing.

On the code side, what do I do? Ideas:

• Use the new persistent-migration Hackage package, which basically does what I do, except there’s no parser
• Keep using my library, but switch from parsed entities to Haskell records
• Fix persistent-parser and maintain a patched version, hoping there aren’t more bugs in there
• Write my own parser

And on the DB side?

• For forge and code, just wipe the DBs
• For dev, go over the tables and manually fix everything
• Whatever code solution I pick, have deeper checks on the migrations! Not just entity names matching but also all the fields and all the unique constraints!

new topic

[See JSON]