DBSight 2.1.1 Free Full-text database search. Free DBSight Lite enables users with basic SQL knowledge to create scalable Lucene search on any database, with arrays of features like Time-based ranking, facet-search, integrated spell checking, suggest-as-you-type, and several pre-built scaffoldings to bootstrap from. You can create a database search service, return results as HTML/XML/JSON/JSONP, so you can easily use it with Ruby, PHP, or any existing web applications. Or you can use the java API to search, and return results in an open-sourced format, defined by the efficient Google Protocol Buffer. It's easily customizable. You can add your own analyzer, similarity for your special needs. It's also highly scalable. You can create sharded indexes for your sharded databases, and have a seamless global search. It's free and super easy. You can create a production-level search in 3 minutes. http://wiki.dbsight.com/index.php?title=Create_Lucene_Database_Search_in_3_minutes By making database full-text search super easy to create or change, you can quickly add a new full-text search or adjust current index structure according to your specific requirements. DBSight makes database searching a detachable separate concern, greatly improves the flexibility and scalability. DBSight also does the "dirty" job to synchronize the database, incremental indexing, facet-search(categorized result counting), easy to change synonyms and stop word, reserved word list, field-level and document-level ranking, multi-threaded searching, time-based ranking, transacdtional index data integrity, server clustering, etc. The latest release is 2.1.1, download the free version here: http://www.dbsight.net/index.php?q=node/47

DBSight obviously can't handle dates or timestamps before January 1st, 1970 or after November 16th 5138, 9:46:39 UTC. Obviously, it breaks on negative values in java.util.Date and throws a RuntimeException with message "time too early" from the VMTool class. I'm not really sure about the "time too late" exception, which is thrown from year 5138 and later.

DBSight obviously can't handle dates or timestamps before January 1st, 1970 or after November 16th 5138, 9:46:39 UTC. Obviously, it breaks on negative values in java.util.Date and throws a RuntimeException with message "time too early" from the VMTool class. I'm not really sure about the "time too late" exception, which is thrown from year 5138 and later.

Hi, Tor-Einar Jarnbjo, Thanks for testing it out! The date can only support what JDK can support. However, you can configure DBSight to treat the special date as a String, when you selecting date out of database, or simply convert the date as a string just by SQL. You can easily avoid this problem.

<blockquoteThe date can only support what JDK can support. However, you can configure DBSight to treat the special date as a String, when you selecting date out of database, or simply convert the date as a string just by SQL. You can easily avoid this problem.</blockquote> I am not sure what you mean? The JDK Date class can of course handle dates before 1970 (the "milliseconds since Jan 1st 1970" value is simply negative), so that the valid range is from year 292269055 BC to 292278994 AC. If DBSight restricts this from 1970 to 5138, it is not because of a JDK limitation.

I reproduced the problem. Sorry, not really a JDK limitation. But rather a "search" limitation. In order to make date time sortable, it requires the time to be positive. And DBSight currently put a limit of 1000 years, for more efficient search. We can easily change the behavior. However, you can easily avoid this by using SQL to cast the datetime as a String.

FYI: 2.1.3beta release added support for time before 1970 So you don't need to cast the earlier time to string now.