From: Richard Acero <lilnemoinslumber@ya...> - 2004-08-25 00:45:17
>Neither of these will work. The above is clearly
>November 1, 2004;
> it"s a specific day. The below is clearly March 21,
>2004; also a
> specific day. This is a problem trying to match
>bibliographic dates to
> data models designed for banks.
> I don"t know the solution, but one is to throw out
> and store it some other way. There is one schema
> seasons something like 2000-21.
I understand what you're saying, I was just throwing
out an idea that would allow the db to hold an
approximate of the date as well as the text. I just
don't know that Morbus is going to move away from SQL
just to allow for this. I'm trying to find the middleground.
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
From: Bruce D'Arcus <bdarcus@fa...> - 2004-08-25 01:43:10
On Aug 24, 2004, at 8:44 PM, Richard Acero wrote:
> I'm trying to find the middleground.
That's cool. I'm just pointing out the issues here, and they're not
terribly obscure. If an undergrad student wants to store citation
information for their term papers, they need to be able to accurately
store dates that simply don't always conform to YYYY-MM-DD. And just
dumb text strings aren't too helpful.
Likewise, movie dates are usually just YYYY, IIRC.