Skip to content
New issue

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

Is IHP useful when the application requires a graph database? #1826

Open
xeruf opened this issue Sep 25, 2023 · 2 comments
Open

Is IHP useful when the application requires a graph database? #1826

xeruf opened this issue Sep 25, 2023 · 2 comments

Comments

@xeruf
Copy link

xeruf commented Sep 25, 2023

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?

@mpscholten
Copy link
Member

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.

@CSchank
Copy link
Contributor

CSchank commented Sep 30, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants