|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.446 2008/09/08 00:47:40 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.447 2008/09/11 17:32:33 tgl Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="functions"> |
4 | 4 | <title>Functions and Operators</title> |
@@ -5187,7 +5187,12 @@ SELECT SUBSTRING('XY1234Z', 'Y*?([0-9]{1,3})'); |
5187 | 5187 | </itemizedlist> |
5188 | 5188 | </para> |
5189 | 5189 | <para> |
5190 | | - Attempting to construct a date using a mixture of ISO week and Gregorian date fields is nonsensical, and could yield unexpected results. In the context of an ISO year, the concept of a 'month' or 'day of month' has no meaning. In the context of a Gregorian year, the ISO week has no meaning. Users should take care to keep Gregorian and ISO date specifications separate. |
| 5190 | + Attempting to construct a date using a mixture of ISO week and |
| 5191 | + Gregorian date fields is nonsensical, and will cause an error. In the |
| 5192 | + context of an ISO year, the concept of a <quote>month</> or <quote>day |
| 5193 | + of month</> has no meaning. In the context of a Gregorian year, the |
| 5194 | + ISO week has no meaning. Users should take care to keep Gregorian and |
| 5195 | + ISO date specifications separate. |
5191 | 5196 | </para> |
5192 | 5197 | </listitem> |
5193 | 5198 |
|
|