MySQL 3.23 uses different date_format()

VERIFIED FIXED in Bugzilla old

Status

()

Bugzilla
Creating/Changing Bugs
P3
enhancement
VERIFIED FIXED
19 years ago
6 years ago

People

(Reporter: miri, Assigned: Tara Hernandez)

Tracking

unspecified
Bugzilla old
Other
Linux

Details

(Reporter)

Description

19 years ago
We're running Bugzilla for our internal use and when we upgraded (we have to)
MySQL to 3.23.x, Bugzilla started to print "Opened: Y-m-d H:m" at bug detail
form instead of "Opened: 2000-12-12 12:23". It's because function date_format is
changed in 3.23, you have to use "%Y-%m-%d" instead.
I don't know if it's possible to fix this (like fetching MySQL version at start
and send Y or %Y depending on its value), I just wanted to let you know.

Comment 1

18 years ago
tara@tequilarista.org is the new owner of Bugzilla and Bonsai.  (For details,
see my posting in netscape.public.mozilla.webtools,
news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)
Assignee: terry → tara

Comment 2

18 years ago
what version of bugzilla were you using?

Comment 3

18 years ago
Adding default QA contact to all open Webtools/Bugzilla bugs lacking one.
Sorry for the spam.
QA Contact: matty
miri@punknet.cz, is this still an issue?

If I don't hear a reply I'll close this out in a month ...

I believe we have checks for the version of dependent software now whereas we
didn't before.  If this still happens in 2.12 after running checksetup.pl I'd
like to hear about it ...
Reporter hasn't touched this bug in over 15 months.  The exiting select statement 
in bug_form.pl does this:

        date_format(creation_ts,'%Y-%m-%d %H:%i'),

it WORKSFORME on MySQL 3.23.38 and MySQL 3.22.18.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
ok...  I'm gonna mark this FIXED instead of WORKSFORME. (explanation in a moment)
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
I am unable to find any other bug that mentions this problem, however, I found 
this change in the cvs logs dated 2000-03-07 (4 days after this bug was filed) 
checked in by terry.  I suspect this was fixed probably based on this bug and 
Terry forgot to close it.
Status: REOPENED → RESOLVED
Last Resolved: 17 years ago17 years ago
Resolution: --- → FIXED
verif. fixed based on examination of source.  moving to Bugzilla product.
Status: RESOLVED → VERIFIED
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Target Milestone: --- → Bugzilla old
Version: other → unspecified
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.