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
{{ message }}
Repository navigation
Inconsistency fetching date properties (http json) #1369
Date fields should be transferred as JSON Date representation,
independently if its an adhoc property, an explicitly declared property with or without an index
Actual behavior
In adhoc-mode its stored and fetched as date object.
If the property is declared as date object, its returned as malformatted Unix-time integer, if (and only) accessed via in/out.
Steps to reproduce
create vertex type my_v1
create vertex type my_v3 extends my_v1
create edge type my_e1
CREATE PROPERTY my_v3.datum DATE
INSERT INTO my_v3 CONTENT {"datum":"2014-05-06","a":"eins"} # --> #175:0
INSERT INTO my_v3 CONTENT {"datum":"2024-05-06","a":"zwei" # --> #176:0
create edge my_e1 from #175:0 to #176:0
select from my_v3 where a='eins'
=> [{:@rid=>"#175:0", :@type=>"my_v3", :@cat=>"v", :datum=>"2014-05-06 00:00:00", :a=>"eins"}]
# datum is a Date object
select out('my_e1') from #175:0
--> {:datum=>#<Date: 2024-05-06 ((2456784j,0s,0n),+0s,2299161j)>, :a=>"eins", :rid=>"#176:0"}
# OK if no date property is present
---> [{:"out()"=>[{:datum=>1714953600000, :a=>"zwei", :@cat=>"v", :@type=>"my_v3", :@rid=>"#176:0"}]}]
# Unix time if a property is declared
Activity
chore(deps): bump jline.version from 3.30.4 to 3.30.5 [skip ci]
gramian commentedon Oct 21, 2025
I cannot reproduce this issue, so this seems to be fixed. @lvca can this issue be closed then?
lvca commentedon Oct 21, 2025
It should be fixed, closing it.
chore(deps): bump neo4j-driver from 6.0.1 to 6.1.0 in /e2e-js [skip ci]
chore(deps): bump jline.version from 3.30.4 to 3.30.5 [skip ci]
chore(deps): bump neo4j-driver from 6.0.1 to 6.1.0 in /e2e-js [skip ci]
chore(deps): bump the github-actions group with 2 updates [skip ci]