npgsql - Npgsql2: [#1010746] NpgsqlDate.AddMonths(m):

Поиск
Список
Период
Сортировка
От fxjr@pgfoundry.org (User Fxjr)
Тема npgsql - Npgsql2: [#1010746] NpgsqlDate.AddMonths(m):
Дата
Msg-id 20100108023258.660F31071FC8@pgfoundry.org
обсуждение исходный текст
Список 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)

В списке pgsql-committers по дате отправления:

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: pgsql: Fix (some of the) breakage introduced into query-cancel
Следующее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Fix oversight in EvalPlanQualFetch: after failing to lock a tuple