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.



---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
      choose an index scan if your joining column's datatypes do not

Reply via email to