trouble caused by change in 7.3 handling of '' in integer context

Поиск
Список
Период
Сортировка
От Vivek Khera
Тема trouble caused by change in 7.3 handling of '' in integer context
Дата
Msg-id x7n0n3doku.fsf@onceler.kciLink.com
обсуждение исходный текст
Ответы Re: trouble caused by change in 7.3 handling of '' in  (Larry Rosenman <ler@lerctr.org>)
Re: trouble caused by change in 7.3 handling of '' in  ("scott.marlowe" <scott.marlowe@ihs.com>)
Re: trouble caused by change in 7.3 handling of '' in integer  (Bruce Momjian <pgman@candle.pha.pa.us>)
trouble caused by change in 7.3 handling of '' in integer context  (Lee Kindness <lkindness@csl.co.uk>)
Список pgsql-general
I see in the 7.3 HISTORY file this:

     * An empty string ('') is no longer allowed as the input into an
       integer field. Formerly, it was silently interpreted as 0.

This is causing major issues with the Request Tracker program
<http://www.bestpractical.com/rt>.

The author has gone so far as to notify all current users that
Postgres 7.3 is not usable with RT, and to stick to 7.2, or to use
MySQL.

Apparently, there is a lot of work that will be necessary to retrofit
RT to this change.  Is there any way possible to make this a logged
warning rather than a fatal so that there is time to transition the RT
code?  I didn't see any notice in any prior release of the upcoming
change.

This unfortunately locks me into the 7.2 line until (if) RT can be
fixed up, and I could really use the 7.3 improvements for my other
applications.

Thanks.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.                Khera Communications, Inc.
Internet: khera@kciLink.com       Rockville, MD       +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera   http://www.khera.org/~vivek/

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

Предыдущее
От: Joe Conway
Дата:
Сообщение: Re: Measuring CPU time use? (Another stupid question)
Следующее
От: Larry Rosenman
Дата:
Сообщение: Re: trouble caused by change in 7.3 handling of '' in