postgres

Commit Graph

Author	SHA1	Message	Date
Bruce Momjian	1934055cbe	Please find a small patch to fix the brain damage "century" and "millennium" date part implementation in postgresql, both in the code and the documentation, so that it conforms to the official definition. If you do not agree with the official definition, please send your complaint to "pope@vatican.org". I'm not responsible for them;-) With the previous version, the centuries and millenniums had a wrong number and started the wrong year. Moreover century number 0, which does not exist in reality, lasted 200 years. Also, millennium number 0 lasted 2000 years. If you want postgresql to have it's own definition of "century" and "millennium" that does not conform to the one of the society, just give them another name. I would suggest "pgCENTURY" and "pgMILLENNIUM";-) IMO, if someone may use the options, it means that postgresql is used for historical data, so it make sense to have an historical definition. Also, I just want to divide the year by 100 or 1000, I can do that quite easily. BACKWARD INCOMPATIBLE CHANGE Fabien Coelho - coelho@cri.ensmp.fr	22 years ago
Tom Lane	1a908a00b0	Fix datetime input parsing to accept YYYY-MONTHNAME-DD and related syntaxes, which had been unintentionally broken by recent changes to tighten up the DateStyle rules for all-numeric date input. Add documentation and regression tests for this, too.	23 years ago
Thomas G. Lockhart	0d93504c40	Add regression tests for date, time, and time with time zone types. Modify date->timestamp conversion to use mktime(). This should do better than before around Daylight Savings Time transitions.	26 years ago

Author

SHA1

Message

Date

Bruce Momjian

1934055cbe

Please find a small patch to fix the brain damage "century" and

"millennium" date part implementation in postgresql, both in the code
and the documentation, so that it conforms to the official definition.
If you do not agree with the official definition, please send your
complaint to "pope@vatican.org". I'm not responsible for them;-)

With the previous version, the centuries and millenniums had a wrong
number and started the wrong year. Moreover century number 0, which does
not exist in reality, lasted 200 years. Also, millennium number 0 lasted
2000 years.

If you want postgresql to have it's own definition of "century" and
"millennium" that does not conform to the one of the society, just give
them another name. I would suggest "pgCENTURY" and "pgMILLENNIUM";-)

IMO, if someone may use the options, it means that postgresql is used for
historical data, so it make sense to have an historical definition. Also,
I just want to divide the year by 100 or 1000, I can do that quite easily.

BACKWARD INCOMPATIBLE CHANGE

Fabien Coelho - coelho@cri.ensmp.fr

22 years ago

Tom Lane

1a908a00b0

Fix datetime input parsing to accept YYYY-MONTHNAME-DD and related syntaxes,

which had been unintentionally broken by recent changes to tighten up the
DateStyle rules for all-numeric date input.  Add documentation and
regression tests for this, too.

23 years ago

Thomas G. Lockhart

0d93504c40

Add regression tests for date, time, and time with time zone types.

Modify date->timestamp conversion to use mktime().
 This should do better than before around Daylight Savings Time
 transitions.

26 years ago

3 Commits (2674bbbe9960f3fb73ecfe771f3cdffe7dc8f1d4)