Re: CF app feature request

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CF app feature request
Date: 2018-12-23 12:09:31
Message-ID: CABUevEzFjC_rOMvaLDL9Ha4=5n94AqS1bEyxuDB5gJzRoGn-mA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 20, 2018 at 7:19 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Magnus Hagander <magnus(at)hagander(dot)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.

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2018-12-23 14:33:23 Re: Speeding up text_position_next with multibyte encodings
Previous Message Magnus Hagander 2018-12-23 11:50:29 Re: CF app feature request