Re: Storing an ordered list

On Tue, Jul 25, 2006 at 22:58:47 -0400, Michael Artz <mlartz@gmail.com> wrote:
> 
> I figure that one choice is to explicitly code the order as an integer
> column in the predicate table which has the advantage of being very
> easy and fast to query/order but *very* slow to reorder as all of the
> predicates need to be updated.  This would seem to be a postgres/MVCC
> weak spot as well.  Example:

If you use numeric instead of int, then it is easy to insert new values.