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

Timestamps should always be two or none #60

Open
tomdemeyer opened this issue Jan 13, 2016 · 7 comments
Open

Timestamps should always be two or none #60

tomdemeyer opened this issue Jan 13, 2016 · 7 comments

Comments

@tomdemeyer
Copy link

When only validSince is given, add validUntil in the far future on import;
When only validUntil is given, add validSince in the far past on import.

@bertspaan
Copy link
Member

I don't think I agree: seems like something you would do on application level, or in queries.

@tomdemeyer
Copy link
Author

makes cypher queries very elaborate; I cannot see a use-case where you would want to have one but not the other..
… and if you need such a thing, ignoring the offending timestamp is easy if it is 0 or 10000000 (for instance)

Tom Demeyer
Waag Society
http://waag.org

On 13 Jan 2016, at 16:21, Bert Spaan [email protected] wrote:

I don't think I agree: seems like something you would do on application level, or in queries.


Reply to this email directly or view it on GitHub.

@bertspaan
Copy link
Member

Ok, if you mean adding always two timestamps for Neo4j PITs, then I agree.

@tomdemeyer
Copy link
Author

Mmmm. Maybe.
If you do a query for concurrent events you’ll never want to see PITS without any time info.
When one of the two is present, it signals time info was provided..
Of course all also possible in the api.. At the moment I ignore all pits with both NULLs very easily.

Hack the knot but through & let me know.

Tom Demeyer
Waag Society
http://waag.org

On 13 Jan 2016, at 16:29, Bert Spaan [email protected] wrote:

Ok, if you mean adding always two timestamps for Neo4j PITs, then I agree.


Reply to this email directly or view it on GitHub.

@bertspaan
Copy link
Member

No, I think it's a good idea, I didn't realize you meant the Neo4j-only timestamps!

@sbocconi
Copy link

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?
Straten met datum van aanleg worden niet teruggevonden (o.a. in De Rijp). Zoeken op meerdere dimensies die in verschillende datasets voorkomen. Bij geometrie in set 1 en tijd in set 2 levert als resultaat altijd '0'.

@tomdemeyer
Copy link
Author

No, different issue..

Tom Demeyer
Waag Society
http://waag.org

On 20 Jan 2016, at 11:45, Stefano Bocconi [email protected] wrote:

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?
Straten met datum van aanleg worden niet teruggevonden (o.a. in De Rijp). Zoeken op meerdere dimensies die in verschillende datasets voorkomen. Bij geometrie in set 1 en tijd in set 2 levert als resultaat altijd '0'.


Reply to this email directly or view it on GitHub #60 (comment).

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

No branches or pull requests

3 participants