Rick, could create a test case and fix it exactly as you suggested, https://github.com/neo4j/community/commit/807d5f7df51b91150fe4349108c3f34af871b6b4
Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Tue, Jun 14, 2011 at 11:55 PM, Peter Neubauer <peter.neuba...@neotechnology.com> wrote: > Rick, > created a ticket for it, will try to write a testcase for it tomorrow > and track it. We are testing Lighthouse for tickets, see > http://neo4jdb.lighthouseapp.com/projects/77609-neo4j-community/tickets/8-make-querying-before-1970-in-lucene-timeline-possible > > Cheers, > > /peter neubauer > > GTalk: neubauer.peter > Skype peter.neubauer > Phone +46 704 106975 > LinkedIn http://www.linkedin.com/in/neubauer > Twitter http://twitter.com/peterneubauer > > http://www.neo4j.org - Your high performance graph database. > http://startupbootcamp.org/ - Öresund - Innovation happens HERE. > http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. > > > > On Tue, Jun 14, 2011 at 8:49 PM, Rick Bullotta > <rick.bullo...@thingworx.com> wrote: >> If no lower bound is provided on a LuceneTimeline query, a default value of >> 0L is used. This will not allow querying of values prior to January 1st, >> 1970. Perhaps it should be -Long.MAX_VALUE instead? >> >> _______________________________________________ >> Neo4j mailing list >> User@lists.neo4j.org >> https://lists.neo4j.org/mailman/listinfo/user >> > _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
