Re: Best way to handle table trigger on update

From: Scott Ribe <scott_ribe(at)killerbytes(dot)com>
To: Justin Pasher <justinp(at)newmediagateway(dot)com>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Best way to handle table trigger on update
Date: 2006-02-01 19:12:37
Message-ID: C0065635.3FCEF%scott_ribe@killerbytes.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I do something similar, and I have the front end generate updates to the
position column of all rows, executed in a single transaction. Then you can
fiddle around with the options and tradeoffs of how to ensure in the db that
no update is accepted that violates the constraints...

--
Scott Ribe
scott_ribe(at)killerbytes(dot)com
http://www.killerbytes.com/
(303) 665-7007 voice

In response to

Browse pgsql-general by date

  From Date Subject
Next Message MargaretGillon 2006-02-01 19:35:53 Re: Concatenated VARCHAR becomes TEXT in view
Previous Message Martijn van Oosterhout 2006-02-01 19:00:50 Re: Concatenated VARCHAR becomes TEXT in view