Re: Any hope for more specific error message for "value too long..."?

Поиск
Список
Период
Сортировка
От Ken Tanzer
Тема Re: Any hope for more specific error message for "value too long..."?
Дата
Msg-id CAD3a31Wki-VWezw6n6XYfc7gCTGmX3W+t22AzJc-vs4PHdMEsQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Any hope for more specific error message for "value too long..."?  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Any hope for more specific error message for "value too long..."?  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
I dug in the archives and came across a crude POC hack here:

https://www.postgresql.org/message-id/21693.1478376334@sss.pgh.pa.us

At the time I didn't want to pursue it further because of Andres'
pending work on redoing expression execution, but that's landed now.

                        regards, tom lane


For that matter, it's not totally
clear what would constitute an improvement --- what do you wish it would
show you, exactly?  

It looks like that patch is about showing which value or where in the statement the error is being caused.  At least for my case, it would be helpful to know which field is causing the error.  And just guessing, but maybe simpler?  I'd be happy to see:

The error text was: ERROR for field [field_name]:  value too long for type character varying(10)

Cheers,
Ken


--
AGENCY Software  
A Free Software data system
By and for non-profits
(253) 245-3801

learn more about AGENCY or
follow the discussion.

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

Предыдущее
От: Vitaliy Garnashevich
Дата:
Сообщение: Re: shared_buffers 8GB maximum
Следующее
От: hmidi slim
Дата:
Сообщение: Join query