| commit | ab6a8b17eb9cd0a18d43ddb20ba33102fa50405e | |
| author | tgl <tgl> | |
| Wed, 10 Jun 2009 05:05:03 +0000 (10 05:05 +0000) | ||
| committer | tgl <tgl> | |
| Wed, 10 Jun 2009 05:05:03 +0000 (10 05:05 +0000) | ||
| tree | 8e1662716c6062f662ba3d13385775174445d19c | treesnapshot (tar.gz zip) |
| parent | d2a70156bb6da7df030e989a97f5613826e546ea | commitdiff |
Make handling of INTERVAL DAY TO MINUTE and INTERVAL DAY TO SECOND input
more consistent with other cases, by having an unlabeled integer field
be treated as a number of minutes or seconds respectively. These cases
are outside the spec (which insists on full "dd hh:mm" or "dd hh:mm:ss"
input respectively), so it's not much help to us in deciding what to do.
But with this change, it's uniformly the case that an unlabeled integer
will be considered as being a number of the interval's rightmost field.
The change also takes us back to the 8.3 behavior of throwing error
for certain ambiguous inputs such as INTERVAL '1 2' DAY TO MINUTE.
Per recent discussion.
more consistent with other cases, by having an unlabeled integer field
be treated as a number of minutes or seconds respectively. These cases
are outside the spec (which insists on full "dd hh:mm" or "dd hh:mm:ss"
input respectively), so it's not much help to us in deciding what to do.
But with this change, it's uniformly the case that an unlabeled integer
will be considered as being a number of the interval's rightmost field.
The change also takes us back to the 8.3 behavior of throwing error
for certain ambiguous inputs such as INTERVAL '1 2' DAY TO MINUTE.
Per recent discussion.
| src/backend/utils/adt/datetime.c | diffblobblamehistory | |
| src/test/regress/expected/interval.out | diffblobblamehistory |