Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

SQLite

Name: The Amazing Anus !tly/rANUS. 2009-08-15 14:23

SQLite.  What do you think of it?

[ ] Yes, SQLite is sufficient for anus haxxing.
[ ] No, SQLite is insufficient for anus haxxing.

Name: Anonymous 2009-08-15 14:40

I don't see the difference between this and MySQL.

Name: Anonymous 2009-08-15 15:04

sqlite is close to being as useful as SQL is going to get. I use it all the time.

>>2
Hush, child. The grownups are talking.

Name: Anonymous 2009-08-15 15:08

I use SQLite as an embedded database for my program, and it's not bad for that purpose. The untyped storage thing is a bit odd, though.

Name: The Amazing Anus !tly/rANUS. 2009-08-15 15:18

>>3,4
Cool.  Is there anything about it that would make you guys want to choose a different SQL implementation if you were working on something really important ?

Name: Anonymous 2009-08-15 15:24

>>5
If database load is so significant that it'd be a good idea to split it off to a separate database server, or if several different applications have to interact with one central database at the same time, I would consider a more ``traditional'' server/client database like Postgres.

I write a lot more applications that use databases in the same way Firefox and progscrape use them, though, for which a serverless SQL implementation like sqlite is perfect.

Name: Anonymous 2009-08-15 15:28

>>3
say that to my face fucker and not online and see what happens

Name: Anonymous 2009-08-15 15:51

>>7
I wish I had a face fucker.

Name: Anonymous 2009-08-15 16:08

>>5
This is really the crucial question. MySQL and Postgres have way too much overhead for a neat little script that only runs on your desktop machine, and SQLite is certainly not beefily robust enough to hold up the weight of the internet all by its lonesome self (ie. you shouldn't run a Rails app on it).

If you've already decided on SQL, then it's just a question of where you're deploying your system, really.

Name: Anonymous 2009-08-15 16:40

>>9
Are you implying MySQL is beefily robust enough?
Even for the circumstances described in >>6, if my only options were SQLite and MySQL, I'd pick SQLite every single time. Even if it can't deal with concurrency very well, at least it respects the data.

Name: Anonymous 2009-08-15 18:41

lol y check out http://oggfrog.com/

Name: Anonymous 2009-08-15 19:58

There's not even a reason to go with MySQL anymore, given the shaky future with Sun/Oracle and the fucking retarded-shit licensing used for its official connectors.

Name: Anonymous 2009-08-15 20:07

>>12
There was no reason before the Oracle takeover either.

Name: >>4 2009-08-15 20:56

>>5
It's not great at concurrency. I'd use a proper database¹ for a website, unless it's a small website.

IOW, what >>6 said.
__
¹ This excludes MySQL.

Name: Anonymous 2009-08-16 1:58

>>14
Concurrency is overrated. Multicore programming is a fad.

Name: Anonymous 2009-08-16 2:26

>>15
Looking forward to your CPUs made entirely out of unobtainium, to keep Moore's law intact without multicores.

Name: Anonymous 2009-08-16 10:37

>>16
You don't understand Moore's law.

Name: Anonymous 2009-08-16 14:04

>>17
You haven't looked at the data recently.

Name: ​​​​​​​​​​ 2010-09-07 14:07

Name: Anonymous 2011-02-04 18:15

Don't change these.
Name: Email:
Entire Thread Thread List