Thank for the kind words! It makes me think that the package is useful ![]()
What is the goal? Having the ability to connect / disconnect from database at runtime?
In fact, this update is quite trivial and can (will) be added.
Keep in mind that multi-tenancy is already supported and that in Neo4j, you can manage multiple databases on the same server (Managing Multiple Databases in Neo4j - Developer Guides)
Noted.
I haven’t implement the timestamps macro so it will be with utc_datetime_usec.
In fact, the date format in Neo4j is converted to datetime with microseconds in Elixir so I already get bitten when I used utc_datetime for the example ![]()
I think you’re not going to be the last to have remarks on this point.
In any case, there’s a tradeoff:
- CamelCase enforcing → atom with uppercase are not idiomatic (except for modules…) but valid.
- snake_cased + conversion → you have to switch when you are writing query with seraph or writing query in pure cypher and this can be subject to errors
- snake_cased without conversion → it’s not what’s recommended for Neo4j
One in all, the best thing I can do is to implement all 3, defaulting to CamelCased and add config options to let each user decide what he prefers






















