Re: Proposed patch for sequence-renaming problems - Mailing list pgsql-patches

From Andrew Dunstan
Subject Re: Proposed patch for sequence-renaming problems
Date
Msg-id 433AC92D.1000207@dunslane.net
Whole thread Raw
In response to Re: Proposed patch for sequence-renaming problems  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches

Tom Lane wrote:

>The more I think about it, the more I think that two sets of function
>names might not be such an awful idea.  next_value(), curr_value(), and
>set_value() seem like they'd work well enough.  Then we'd just say that
>nextval and friends are deprecated except when you need late binding,
>and we'd be done.
>
>
>
>

Personally, I like this more than the overloading idea.

cheers

andrew

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proposed patch for sequence-renaming problems
Next
From: Gavin Sherry
Date:
Subject: Re: Proposed patch for sequence-renaming problems