-
Notifications
You must be signed in to change notification settings - Fork 3
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
Timestamps should always be two or none #60
Comments
I don't think I agree: seems like something you would do on application level, or in queries. |
makes cypher queries very elaborate; I cannot see a use-case where you would want to have one but not the other.. Tom Demeyer
|
Ok, if you mean adding always two timestamps for Neo4j PITs, then I agree. |
Mmmm. Maybe. Hack the knot but through & let me know. Tom Demeyer
|
No, I think it's a good idea, I didn't realize you meant the Neo4j-only timestamps! |
Is this issue from Trello related: zoeken op before and after: plan maken voor huidige beperkingen"ik wil inzoomen op een bounding box en dan met slider door de tijd kunnen lopen en zien wat er bij komt en af gaat." "Open einde" records worden niet gevonden. Wanneer is dat een probleem en hoe lossen we dat dan op? |
No, different issue.. Tom Demeyer
|
When only
validSince
is given, addvalidUntil
in the far future on import;When only
validUntil
is given, addvalidSince
in the far past on import.The text was updated successfully, but these errors were encountered: