Leif B. Kristensen wrote:
0 = before (date1),
1 = say (date1),
2 = ca. (date1),
3 = exact (date1),
4 = after (date1),
5 = between (date1) and (date2),
6 = (date1) or (date2),
7 = from (date1) to (date2).
This kind of reeks like a begin/end date and an accuracy quantifier,
though that wouldn't account for option 6.
Your cases 0 to 5 and 7 would be transformed into something like:
date A date B accuracy
0: NULL date1 5
1: date1 date1 3
2: date1 date1 2 (is 'ca.' less accurate than 'say'?)
3: date1 date1 5
4: date1 NULL 5
5: date1 date2 2
7: date1 date2 5
Where I defined '5' as being accurate, and lower values less accurate.
You may want to use values with a wider spread, it'll allow more
fuzziness about how sure you are about a certain date.
Just my 2 centims.
--
Alban Hertroys
[EMAIL PROTECTED]
magproductions b.v.
T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
7500 AK Enschede
// Integrate Your World //
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
