vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| The following bug has been logged online: Bug reference: 2482 Logged by: Alexander Galler Email address: galler@kuzbass.net PostgreSQL version: 8.1.3 Operating system: Windows XP Description: Wrong result in timestamp_in, timestamptz_in, date_in Details: SET SESSION DateStyle TO ISO, YMD; select '20.01.01 BC'::timestamp; Result: "2020-01-01 00:00:00 BC" I want "20-01-01 00:00:00 BC" select '20.01.01 BC'::timestamptz Result: "2020-01-01 00:00:00+06:11 BC" I want "20-01-01 00:00:00+06:11 BC" select '20.01.01 BC'::date Result: "2020-01-01 BC" I want "20-01-01 BC" ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster |
| ||||
| "Alexander Galler" <galler@kuzbass.net> writes: > select '20.01.01 BC'::timestamp; > Result: > "2020-01-01 00:00:00 BC" > I want "20-01-01 00:00:00 BC" You can write select '0020.01.01 BC'::timestamp; I agree it seems like a bug that the 'yy'->'20yy' conversion is applied to BC dates. The code appears to try to avoid that, but I think it's confused in this case because 'BC' hasn't been scanned yet. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
| Thread Tools | |
| Display Modes | |
|
|