jason, how about blowing away the records from the db table and re-inserting them? (using the new prioty index)
this is provided you've got all the data you need for those records to insert them back again and it won't upset any foreign keys... just a thought cheers barry.b > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Jason > Sheedy > Sent: Thursday, 14 April 2005 1:23 PM > To: CFAussie Mailing List > Subject: [cfaussie] RE: ordering records by priority > > > On 4/14/05, Steve Onnis <[EMAIL PROTECTED]> wrote: > > you could use a select box with some buttons to move the > items up and down, > > then use the position in the list when it gets submitted to > re order your > > items > > Hi Steve, > I probably wasn't very clear in my description because I didn't go > into the actual method of displaying it, but that's kind of what I'm > doing. I just have 4 buttons on each item, (top,up,down,bottom). > > My question was more to do with the method of storing the priority to > make it more efficient in terms of database access. I don't want to > have to update every record every time I change the priority on an > item. > > -- > Jason Sheedy > www.jmpj.net > > --- > You are currently subscribed to cfaussie as: [EMAIL PROTECTED] > To unsubscribe send a blank email to > [EMAIL PROTECTED] > Aussie Macromedia Developers: http://lists.daemon.com.au/ > --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
