Issue 21721 - YEAR is not correctly formated
Summary: YEAR is not correctly formated
Status: CLOSED WONT_FIX
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1
Hardware: PC Linux, all
: P4 Trivial (vote)
Target Milestone: ---
Assignee: Frank Schönheit
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-26 09:23 UTC by mpupat
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description mpupat 2003-10-26 09:23:47 UTC 
WHen you use a year field in MySQL it appears as DD/MM/YY instead of 
YYYY in OOo bydefault.
Comment 1 Frank Schönheit 2003-10-27 08:59:20 UTC 
sorry, but this is rather unlikely to be changed. The problem here is
that OOo does not focus on a particular database like MySQL, but on a
subset which is shared across different databases, so the user is not
bound to a certain database.
YEAR is a non-standard extension of MySQL, which currently cannot be
transported via the OOo API. Extending this API with things which are
special to a particular database is not a good idea, since it would
macerate OOo's idea of database independence.

Additionally, since you should easily be able to work around this by
changing the formatting manually, or to bind the column to a numeric
field, the benefit does not seem worth the effort to me.
Comment 2 Frank Schönheit 2003-10-27 08:59:38 UTC 
closing WONTFIX
Comment 3 hans_werner67 2004-02-02 12:59:48 UTC 
change subcomponent to 'none'