= 27d567bc2d48d9f40e9ccc20ea370b15)
gjm comments on Lesswrong Potential Changes - Less Wrong Discussion
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (88)
Very funny.
If what should be straightforward SQL queries are too difficult to implement, LW code base is FUBARed anyway.
Anyone wants to write another middle layer which will implement normal SQL on top of that key-value store implemented on top of normal SQL? X-D
A bit more seriously, LW code clearly uses some ORM which, hopefully, makes some sense in some (likely, non-SQL) way. Also reading is not writing and for certain tasks it might make sense to read the underlying Postgres directly without worrying about the cache.