Bug 2415 - implement interval seconds precision for INTERVAL SECOND
Summary: implement interval seconds precision for INTERVAL SECOND
Status: NEW
Alias: None
Product: SQL
Classification: Unclassified
Component: all (show other bugs)
Version: -- development
Hardware: x86 (i?86) Linux
: --- enhancement
Assignee: SQL devs
URL: http://sourceforge.net/support/tracke...
Depends on:
Reported: 2006-01-05 03:03 CET by Sjoerd Mullender
Modified: 2016-04-11 11:46 CEST (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Sjoerd Mullender cwiconfidential 2006-01-05 15:03:49 CET
In interval types, the most significant part has a
leading precision, and if seconds are part of the
interval, it also has a seconds precision (number of
digits in the fraction).  This means that an interval
of just second can have both:
with p the interval leading precision and q the
interval seconds precision.

MonetDB/SQL only allows a single value here (presumably
the leading precision, but I'm not sure about that).
Comment 1 Fabian Groffen 2006-01-05 15:14:20 CET
Logged In: YES 

This bug seems to be related to http://sourceforge.net/support/tracker.php?aid=1357338.  The SECONDS
in an interval should be of double type to be able to
represent fractions of seconds.
Comment 2 Fabian Groffen 2006-01-15 10:57:52 CET
Logged In: YES 

This is more like a feature request.  It will at least not
be included in the next release.
Comment 3 Romulo Goncalves 2007-01-17 19:45:14 CET
Logged In: YES 
Originator: NO


WHy this bug is not closed?

Comment 4 Stefan Manegold cwiconfidential 2009-02-17 11:58:14 CET
[ 1357338 ] SQL: EXTRACT returns wrong answer for SECOND
has been closed with "won't fix".

What about this one?
Also "won't fix"?
Or should we rather turn both into a feature request?
Comment 5 Niels Nes cwiconfidential 2009-11-22 23:18:43 CET
moving to feature requests. This requires that we move to 'decimal' types for intervals.
Comment 6 Pseudo user for Sourceforge import 2010-05-04 09:32:09 CEST
This bug was previously known as tracker item 1397758 at http://sourceforge.net/support/tracker.php?aid=1397758