Issue 18758 - Prompted Querys should always accept unambigious Date/Time formats (ISO notation)
Summary: Prompted Querys should always accept unambigious Date/Time formats (ISO notat...
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC3
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-28 02:44 UTC by jeffos2
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description jeffos2 2003-08-28 02:44:24 UTC
This issue arose from Issue 18594 where the responder indicated that this
should be considered as an enhancement.

When prompted for Date/Time variables, the parser should be prepared to accept
unambigious input for Date/Time fields reguardless of the Locale.

For example, the string:
<digit><digit><digit><digit><delimiter>[<digit>]<digit><delimeter>[<digit>]
<digit>

can always (I think but don't really know) be safely parsed as YYYY/MM/DD.
Comment 1 Frank Schönheit 2003-08-28 08:15:07 UTC
Jeffery, thanks for filing this. The notation you refer to
(YYYY-MM-DD) is know as ISO notation :) - adding this to the summary

fs->oj: This is related to the internal bug 109202 - but neither of
the two is a real duplicate of the other one.

re-assigning, confirming, targeting
Comment 2 Frank Schönheit 2003-08-28 08:23:45 UTC
noticed a little bit too late that you talked about a general
delimiter, not only '-'. I am uncertain if this would be a good idea,
since I don't know the relevance of other delimiters 'd' in a
YYYYdMMdDD notation.

E.g. (correct me if I'm wrong) the usual format for the english-us
locale is DD/MM/YYYY - is YYYY/MM/DD really used?
Furthermore, there may be locales (I don't know, but OOo supports such
a huge amount of them, that we cannot be sure :) where the *default*
notation would be YYYY.DD.MM - who knows? In such a locale, accepting
YYYY.MM.DD would be disastrous.

IOW, I tend to saying we should accept the ISO notation, but not
arbitrary delimiters, as we maybe cannot guarantee that this is
unambiguous in all locales.
Comment 3 ocke.janssen 2003-08-28 12:34:01 UTC
For english locales the format is MM/DD/YYYY.
Comment 4 jeffos2 2003-08-29 00:46:45 UTC
Well, I certainly am not going to speak for the entire
English speaking world. :-) But here in the USA MM/DD/YYYY
is the common format, two digit year with leading zeros
ommited for MM and DD being the most common. But the YYYY/MM/DD
format is also seen frequently.

I agree with your example and conclusion and will be happy with
a solution that allows ISO formats.

Thanks,
Jeff


Comment 5 ocke.janssen 2003-08-29 08:11:49 UTC
The parser now accepts also the ISO format YYYY-MM-DD.
If you want this to work in your current installtion, you have to
select your table in the broser (F4) and change the format of the date
column (right mousr click on header) to ISO. After that, you can enter
ISO format into the query design.

Fixed in CWS oj07

Best regards,

Ocke
Comment 6 hans_werner67 2004-02-02 12:23:27 UTC
change subcomponent to 'none'
Comment 7 ocke.janssen 2004-02-10 11:01:55 UTC
.
Comment 8 marc.neumann 2004-02-11 11:02:11 UTC
verify in cws oj07
Comment 9 marc.neumann 2004-02-11 11:02:28 UTC
verify in cws oj07
Comment 10 marc.neumann 2004-04-27 10:09:05 UTC
Hi,

fixed in current developer build -> close.
The current developer build can be found at
http://download.openoffice.org/680/index.html
Feel free to reopen if this issue is not fixed in the developer build.

Bye Marc