I'd vote for the date-range as that can be indexed and result in fast retrieval.
The separate column for accuracy would be a computed range and not indexable. Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems ________________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of Oliver Schneider [sqlite-mailingl...@f-prot.com] Sent: Tuesday, August 07, 2012 9:46 AM To: sqlite-users@sqlite.org Subject: EXT :[sqlite] Suggestions for approximate date Hello, I have a decision to make about how to store dates that may not be entirely accurate inside an SQLite DB. There are two options I came up with: 1. store "exact" date plus (in separate column) value for accuracy 2. store date range corresponding to original accuracy The accuracy can be exact date, only month and year, +/- 1 year, +/- 10 years, +/- 50 years. I reckon for searching the second option could be better. Does anyone here have any better ideas? I'd go for the Julian Day stored as REAL in either case. Thanks, // Oliver _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
