Can anyone say when Oracle is justified? I have yet to encounter a problem the postgres or mysql didn't support but alas I have not worked on everything.
"SQLite is not designed to replace Oracle. It is designed to replace fopen()."
21–30 of 58 posts
Re: "SQLite is not designed to replace Oracle. It is designed to replace fopen()."
#22Earlier quoted context omitted.
Agreed. And the database can grow surprisingly large (multi GB with many millions of rows) and it still performs quite well.
This surprises me. Though I've used it with great success for several small projects, my only experience with SQLite on anything remotely large was a Rails app with maybe a million records in the DB. Over time, performance became very slow and switching to MySQL made a world of difference. At the time, I attributed it to SQLite, but now I'm wondering if it was Rails or (more likely) my inexperience at optimizing perf…
In SQLite, autocommit is on, so if you weren't explicitly setting your transactions, you might have been commit after each update. Also, the standard disk cache is 2MB, so if you think your DB should have more memory than that, up it with default_cache_size.
Re: "SQLite is not designed to replace Oracle. It is designed to replace fopen()."
#23Wow, more projects should have a page similar to this one. Upvoted because it’s good to keep in mind when thinking of sqlite and when documenting your own project.
Re: "SQLite is not designed to replace Oracle. It is designed to replace fopen()."
#24By the use of "an", I learned that I have been pronouncing SQLite wrong. The maintainers clearly prefer the spelling out of SQL in the title. I've always been on the "sequel" side of pronouncing SQL (hey, it's no worse than "scuzzy" for SCSI), which morphed SQLite into "Sequelite". I never realized how bizarre that sounded (almost more like a material than a database).
I and most people I know call it "sequelite". That works for me...
Re: "SQLite is not designed to replace Oracle. It is designed to replace fopen()."
#25Earlier quoted context omitted.
So does that become S-Q-L-ite or S-Q-Lite, you think?
Good point. I was going for SQL-Lite. But being wrong (and hearing enough people say "lie-nux" [and to be clear, I am not mocking ... we read things and form our own pronunciation because we often don't hear them said] ...) I decided to google it. This isn't necessarily authoritative or well researched, but it appears that S-Q-L-Lite is correct: http://blog.cleverly.com/permalinks/247.html
As an aside, to follow Linus' pronunciation, it is Lee-nucks, from the Finnish way of pronouncing "Linus." Americans are used to a different pronunciation of the same name and thus generally adopted a different way of saying "Linux."
Language is fascinating!
Re: "SQLite is not designed to replace Oracle. It is designed to replace fopen()."
#26Can anyone say when Oracle is justified? I have yet to encounter a problem the postgres or mysql didn't support but alas I have not worked on everything.
When you need "nobody ever got fired for buying IBM" levels of nontechnical legitimacy?
(I too wonder what technical marvels it can perform which justify the cost).
Re: "SQLite is not designed to replace Oracle. It is designed to replace fopen()."
#27Earlier quoted context omitted.
Good point. I was going for SQL-Lite. But being wrong (and hearing enough people say "lie-nux" [and to be clear, I am not mocking ... we read things and form our own pronunciation because we often don't hear them said] ...) I decided to google it. This isn't necessarily authoritative or well researched, but it appears that S-Q-L-Lite is correct: http://blog.cleverly.com/permalinks/247.html
As an aside, to follow Linus' pronunciation, it is Lee-nucks, from the Finnish way of pronouncing "Linus." Americans are used to a different pronunciation of the same name and thus generally adopted a different way of saying "Linux." Language is fascinating!
Linus is a native speaker of Swedish, not Finnish.
Re: "SQLite is not designed to replace Oracle. It is designed to replace fopen()."
#28Can anyone say when Oracle is justified? I have yet to encounter a problem the postgres or mysql didn't support but alas I have not worked on everything.
Support. You can properly find some solution to your issue with postgres online. Oracle can send an Oracle certified engineer who can solve your problem.
Consistency. Your enterprise depends on terabytes of hyper valuable information (Wallmart with their sales data), can you guarantee that you won't end up with corruption issues? Or that the next version will work with your system too?
That said as long as you make less than 20 mil/year, Oracle isn't likely to be the best solution.
Just a quick question: which engine do you use for your MySQL system?
Re: "SQLite is not designed to replace Oracle. It is designed to replace fopen()."
#29Earlier quoted context omitted.
As an aside, to follow Linus' pronunciation, it is Lee-nucks, from the Finnish way of pronouncing "Linus." Americans are used to a different pronunciation of the same name and thus generally adopted a different way of saying "Linux." Language is fascinating!
Linus is a native speaker of Swedish, not Finnish.
The Internets confirms this. I didn't know that; I learned something today!
Re: "SQLite is not designed to replace Oracle. It is designed to replace fopen()."
#30Can anyone say when Oracle is justified? I have yet to encounter a problem the postgres or mysql didn't support but alas I have not worked on everything.
Mostly echoing tomjen3 in this, but:
Oracle isn't selling databases. They're selling database support. Similar to how IBM operates - they make good stuff, but you're really not paying for the hardware. If you were, they'd be outrageously expensive compared to something built more simply - see Backblaze, for an example: http://blog.backblaze.com/2009/09/01/petabytes-on-a-budget-h... .