On 4/14/05, Darryl Lyons <[EMAIL PROTECTED]> wrote: > Yeah, if you use a bridging table to store the recordID and priority, then > index that table by "record ID, priority", it would be quite quick. You'd > just have to blow away the data each time in that table and then reinsert. > > Darryl Lyons
Good idea Darryl, but I think that would create just as much load as updating the priority on the original table. I'm pretty sure doing multiple inserts on a virtual index would be more db intensive than multiple updates and you would have to do that even when you move an item up one or down one. You's then have to do a join to display it .. it's starting to get messy. -- 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/
