<- Previous Log | Select Different Log | Next Log -> |
Searching from 2021-02-11 00:00:00 to 2021-02-11 23:59:59.999999. Query completed in 1.00 seconds [2021-02-11 16:02:06] --> Lucifer_arma_ has joined the channel [2021-02-11 16:03:16] <-- Lucifer_arma has quit (Ping timeout: 240 seconds) [2021-02-11 19:40:45] <-- Lucifer_arma_ has quit (Ping timeout: 264 seconds) [2021-02-11 20:36:50] <-- Armanelgtron has quit (No Ping reply in 210 seconds.) [2021-02-11 22:21:20] --> Armanelgtron has joined the channel [2021-02-11 22:21:20] -!- Topic for #armagetron is "http://www.armagetronad.org/ | pastebin: http://armagetron.pastebin.com/ | Tournaments: #armagetron.tourneys | Pickup a game: #armagetron.pickup" [2021-02-11 22:21:20] -!- Topic set by guru3 on 2015-04-22 20:50:50 UTC [2021-02-11 22:21:25] -!- card.freenode.net set mode #armagetron +cnrt [2021-02-11 22:21:25] -!- Channel #armagetron created on 2006-11-26 06:42:45 UTC [2021-02-11 23:44:28] --> Lucifer_arma_ has joined the channel [2021-02-11 23:46:16] <Lucifer_arma_> ]ping [2021-02-11 23:46:17] <ljrbot> pong [2021-02-11 23:46:22] -!- Lucifer_arma_ changed nick to Lucifer_arma [2021-02-11 23:47:36] <Lucifer_arma> Is there any reason a database update function should *not* check to see if the record has been updated before making the write? [2021-02-11 23:47:50] <Lucifer_arma> assuming it has access to the record without having to run an additional query to get it, of course [2021-02-11 23:49:14] <Lucifer_arma> so, if the record hasn't changed, it doesn't do the update. The only thing I can think of that that would affect is the last_changed field. It would mean that someone tried to do an update, it didn't happen because nothing changed, and no record of the attempt to update is made [2021-02-11 23:50:11] <Lucifer_arma> also, I'm far from the 100+ car pileup in Fort Worth, but I'm actually pretty close to the 40+ car pileup in Austin/Cedar Park, but since I don't have a vehicle I could be driving on the freeway, of course I wasn't in itView entire month