database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-29 13:56:47 +03:00
Code

Add a comment to AdjustIntervalForTypmod to reduce chance of future bugs.

Browse Source 
It's not entirely evident how the logic here relates to the
interval_transform function, so let's clue people in that they need to
check that if the rules change.
This commit is contained in:
Robert Haas 2012-02-09 12:22:21 -05:00
parent 6656588575
commit d429ebe347
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/backend/utils/adt/timestamp.c
View File

@ -1069,7 +1069,8 @@ AdjustIntervalForTypmod(Interval *interval, int32 typmod)
* nonzero "month" field. However that seems a bit pointless when we * nonzero "month" field. However that seems a bit pointless when we
* can't do it consistently. (We cannot enforce a range limit on the * can't do it consistently. (We cannot enforce a range limit on the
* highest expected field, since we do not have any equivalent of * highest expected field, since we do not have any equivalent of
* SQL's <interval leading field precision>.) * SQL's <interval leading field precision>.) If we ever decide to
* revisit this, interval_transform will likely requite adjusting.
* *
* Note: before PG 8.4 we interpreted a limited set of fields as * Note: before PG 8.4 we interpreted a limited set of fields as
* actually causing a "modulo" operation on a given value, potentially * actually causing a "modulo" operation on a given value, potentially