If anyone is interested, I wrote a short blog piece on improving "Sortable" performance, by reducing the number of DB hits after "Dropping" elements to a single SQL statement. It's here: http://www.deschutesdigital.com/wordpress/wordpress/?p=26 This problem has dogged me for awhile, as many solutions I've seen, including the one in Chad Fowlers "Rails Recipes" book require a DB UPDATE hit for each element on the list. This is a killer on high-demand app's. I use PostgreSQL's FROM clause in an UPDATE statement to boil it down to a single UPDATE stmt. Maybe someone has solved this before (probably), but I had a hard time figuring it out, and figured that if/when I did, it might help if I posted it somewhere.
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
