| From: | fxjr(at)pgfoundry(dot)org (User Fxjr) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | npgsql - Npgsql2: [#1010746] NpgsqlDate.AddMonths(m): |
| Date: | 2010-01-08 02:32:58 |
| Message-ID: | 20100108023258.660F31071FC8@pgfoundry.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
[#1010746] NpgsqlDate.AddMonths(m): IndexOutOfRangeException, if new date in following year. Applied patches: [#1010747] Correction of NpgsqlDate.AddMonths(m), if new date in following year. Thanks Gildas (prime.gildas @nospam@ gmail.com) for patch and testcase. Also thanks Sibylle Koczian (nulla.epistola @nospam@ web.de) for patch reviewing and testing.
Modified Files:
--------------
Npgsql2/src/NpgsqlTypes:
DateDatatypes.cs (r1.11 -> r1.12)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/NpgsqlTypes/DateDatatypes.cs?r1=1.11&r2=1.12)
Npgsql2/testsuite/noninteractive/NUnit20:
TypesTests.cs (r1.8 -> r1.9)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/testsuite/noninteractive/NUnit20/TypesTests.cs?r1=1.8&r2=1.9)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-01-08 02:44:00 | pgsql: Fix oversight in EvalPlanQualFetch: after failing to lock a tuple |
| Previous Message | Simon Riggs | 2010-01-08 02:11:26 | Re: pgsql: Fix (some of the) breakage introduced into query-cancel |