Feature Requests item #2104442, was opened at 2008-09-10 23:33
Message generated for change (Comment added) made by mr-meltdown
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=482471&aid=2104442&group_id=56967

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 2
Private: No
Submitted By: Stefan de Konink (skinkie)
Assigned to: Nobody/Anonymous (nobody)
>Summary: SQL: different timestamptz format

Initial Comment:
How difficult would it be to accept the following format? A hackish solution 
would be accepted:

2008-07-25T15:54:39


The following is accepted in Monet:

2008-07-25 15:54:39

----------------------------------------------------------------------

>Comment By: Fabian (mr-meltdown)
Date: 2009-12-01 10:32

Message:
This seems like a duplicate of #2539357.  It's just requesting the
timestamp parser to be a bit more flexible.

----------------------------------------------------------------------

Comment By: Fabian (mr-meltdown)
Date: 2008-09-11 08:59

Message:
Is this just because you do a COPY INTO?  (How about sed somewhere in the
pipeline in that case?)  If not, can't you use an SQL string
search-and-replace function to do it?  We try to stick to the (ugly) SQL
standard.

----------------------------------------------------------------------

Comment By: Stefan de Konink (skinkie)
Date: 2008-09-11 00:31

Message:
File Added: iso8601.patch

----------------------------------------------------------------------

Comment By: Stefan de Konink (skinkie)
Date: 2008-09-11 00:05

Message:
To be factually correct it is ISO 8601 combined time date.

    * Date and time represents a specified time of a specified day. When
use is made of the calendar date the representation is: 

YYYY-MM-DDThh:mm:ss

where the capital letter T is used to separate the date and time
components. Thus, for a very precise date and time, look at this:

Example: 2003-04-01T13:01:02 represents one minute and two seconds after
one o'clock in the afternoon of 2003-04-01. 

----------------------------------------------------------------------

Comment By: Stefan de Konink (skinkie)
Date: 2008-09-11 00:01

Message:
We call it XML... it is around us everywhere without any proofs it is an
actual standard. But the acceptation of a space vs 'T' wouldn't be that
hard, I just cannot find how sql_find_subtype/sql_init_subtype defines
this...

----------------------------------------------------------------------

Comment By: Martin Kersten (mlkersten)
Date: 2008-09-10 23:39

Message:
This is hackish. 
What is the rationale? What standard requires this?
What system recognizes this?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=482471&aid=2104442&group_id=56967

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Monetdb-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-bugs

Reply via email to