Re:"SQLite is not designed to replace Oracle. It is designed...
by rbranson on Friday July 29, 2011 @04:15PM
(#2823612)
... because the only use for file I/O in applications is structured tables of data? What about audio/video, documents, graphs, log-structured data, object caches, unstructured flat files, etc? Don't get me wrong, SQLite is awesome, but this is a classic example of the relational database world's pervasive attitude that they are the superior solution for any data storage problem.
[ Parent
| on HN ]
Re:"SQLite is not designed to replace Oracle. It is designed...
by owenmarshall on Friday July 29, 2011 @04:25PM
(#2823655)
Wow. Not only did you manage to completely miss the point of that statement, but you cast it up as a hasty strawman to boot. I'm quite impressed.
The choice of fopen() and Oracle was meant to convey simplicity: SQLite solves problems on the simple end of the difficulty spectrum -- problems you would normally solve with fopen(). It is not for problems at the complex end, like Oracle. It's a simplified expression; reading it literally is foolish.
Re:"SQLite is not designed to replace Oracle. It is designed...
by rbranson on Sunday July 31, 2011 @11:19AM
(#2828503)
Damn, you are so right bro.
Re:"SQLite is not designed to replace Oracle. It is designed...
by andylei on Friday July 29, 2011 @04:51PM
(#2823741)
replace some instances of fopen(), not every instance of fopen()