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
Cause of this bug is that when Halin is first initializing, it has to run certain queries, like getting cluster overview, in order to know how to proceed. By default, halin grabs a session and runs a query on the default database, which fails if the default database isn't active. The issue is, if the default database isn't available to answer queries, Halin can't be sure where else to send the query because it doesn't even have available information on version or multi-db capabilities yet. I'll see what work-around is possible.
I made the same mistake,
The neo4j version is community version 4.2.7, which uses the default library, but the above problems also occur.
My question is, does the community version not support it at all? Or something else?
With 4.x, if you stop the default database and then try to connect with Halin, you get the standard connection error (see screenshot).

The text was updated successfully, but these errors were encountered: