[01:23] evening [01:27] party [01:30] <_stink_> yes [01:35] heh [02:16] cmaloney: get ready for paper day at chc tomorrow [02:16] cmaloney: fancybpaper and two fountain pens show up tomorrow [02:16] one a flex nib! wooo [02:16] geek out...boom.../me does a dance [13:53] morning [13:56] morning [14:56] o/ [15:31] https://www.reddit.com/r/programming/comments/3v4l98/php_7_released/ [22:10] And in "You have got to be fucking kidding me" news: http://stackoverflow.com/questions/603724/how-to-implement-limit-with-microsoft-sql-server [22:12] yup [22:12] newer versions make it easy [22:12] it was REALLY Bad in pre 2005 [22:13] How is it that we have a database server that doesn't understand limit in 2015? [22:13] there is a simple flowchart everone should use when choosing a data storage system. it goes like this: Should I Not Use Postgresql? No, you should use postgresql. [22:13] That's great, save for someone at a company decided to implement their system on this bullshit [22:14] cmaloney: could be worse, could be mongodb [22:14] or... oracle [22:14] mongodb < /dev/null [22:14] oracle < mongodb [22:15] :) [22:15] Hm, I thought Limit was ANSI, but apparently it isn't [22:16] which explains why everyone implements it differently. [22:16] nope [22:16] and since Sybase was pretty much a dog's breakfast anyway, it's no wonder Microsoft partnered with them [22:16] and even if it was, most don't implement the standardd. [22:16] http://dba.stackexchange.com/questions/30452/ansi-iso-plans-for-limit-standardization [22:17] It's heartening that even the Oracle implementation is worse than MSSQL [22:17] No wonder Oracle is performant: you need it to get it to do anything useful. [22:18] i don't even know if it is performant.