Is IHP useful when the application requires a graph database?
xeruf opened this issue · comments
In https://ihp.digitallyinduced.com/Guide/database.html#introduction you clearly state your focus on Postgres, which I kinda understand - though graph databases like ArangoDB also support relational paradigms.
If I want to use a graph database, can IHP still be useful or would you suggest going with another tool in that case?
it could still be useful for the overall web interface. Hard to decide for the general case without more information. Functonality like the database functions, schema designer, migrations, forms, etc. will not work well with the graph database. If you avoid these functions it can work.
I'd do application logic in IHP and then you could interface with a Graph database. If there's a Haskell binding for the specific graph database you want to use, you could easily use that binding in IHP to do the graph-specific stuff, but that part would obviously not be supported by the IHP IDE, etc.