Re: CF app feature request

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Re: CF app feature request
Дата
Msg-id CABUevEzFjC_rOMvaLDL9Ha4=5n94AqS1bEyxuDB5gJzRoGn-mA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: CF app feature request  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers


On Tue, Nov 20, 2018 at 7:19 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Magnus Hagander <magnus@hagander.net> writes:
> I'm trying to figure out where this thread left off :) My understanding of
> the consensus is we don't actually want/need a change in the app, but are
> instead OK with the admin just handling it a somewhat ugly way in the few
> cases where it's necessary?

The original case (just a mistakenly duplicated entry) seems OK to solve
with a quick DELETE on the underlying table.

> Or is the consensus to add a "Withdrawn" status, just to solve a slightly
> different problem from the one that started this thread?

I think there is a use-case for "Withdrawn", it's more polite than
"Rejected" ;-).  But it's not a very high-priority request.

Status "Withdrawn" has now been added. 

--

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

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: CF app feature request
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: Speeding up text_position_next with multibyte encodings