Beats me. But consider that they're advocating SQLite...
Name:
Anonymous2007-07-27 13:33 ID:1h95mwqx
srsly. sqlite is fine w/ 1 hit/sec or for a desktop app used by 1 person, but you need something > sqlite for 4chan. mysql/postgresql are the only options... fer reals.
Name:
Anonymous2007-07-27 13:38 ID:zqTMG8SM
>>6
Because it lacks standard RDBMS features and is fucking slow for anything remotely complicated. Use PostgreSQL.
Name:
Anonymous2007-07-27 13:45 ID:zqTMG8SM
SQLite is awesome for a lot of things, it's fast and easy to deploy/use/manage. It's grate for local applications and also a good choice for very simple web applications.
Name:
Anonymous2007-07-27 13:56 ID:Jp8eArej
Hey guys, let's use flat files. Screw caching!
Name:
Anonymous2007-07-27 14:47 ID:NqZJ055D
>>10 it lacks standard RDBMS features and is fucking slow for anything remotely complicated
What in the fuck, are you still living 10 years ago? That was MySQL 3.23. MySQL 5.0 is fully ACID-compliant with several storage engines, supports unions, subqueries, foreign keys, stored procedures/functions/triggers (though they suck), views, and strict data types, and it has a better optimizer and you don't need to lock before writing securely; in fact, InnoDB doesn't even lock reads when writing to the same row.
>>13
And all that is just a pile of cheap and poorly implemented hacks.
Name:
Anonymous2007-07-27 16:16 ID:t1qDFQ92
>>13
And I'll bet you $5 that 4chan is using MySQL4.
Name:
Anonymous2007-07-27 17:21 ID:YoFfXhCn
Microsoft SQL Server or GTFO
Name:
Anonymous2007-07-27 20:39 ID:NqZJ055D
>>14
InnoDB is not a "poorly implemented hack". Do you actually have any idea of what you're talking about? Many database engines in widespread use today can envy InnoDB's MVCC system.
>>15
Probably, but unlike PHP, MySQL 5 is fully backwards-compatible with MySQL 4 and upgrading from one to another is a snap. Basically, you get extra performance (and more features to use in future development) at no cost of any kind.
Name:
Anonymous2007-07-27 20:43 ID:ouvxLYDB
>>17
Absolutely correct. 14 sounds like a Microsoft/PostgreSQL/Oracle fanboy.
>>6
I don't know, maybe because of GNU/hippies? I don't understand why SQLite is "good" and MySQL is "bad". To me, SQLite, MySQL and PostgreSQL are all good products, which have their advantages and disadvantages, and different uses in the case of SQLite.
>>19
What? Those fags got it wrong. If you use InnoDB with its default options, it's fully ACID-compliant. You can give up on up to a second of data to increase performance a lot (like in any database) by setting innodb_flush_log_at_trx_commit to 0, but that's not even its default value.
faggot, no need to keep its handle because next call to mysql_pconnect will reuse it, but persistent connections work like shit and are not recommended, besides MySQL takes microseconds to open a connection
>>40
faggot, i'm not sure if I completely believe that, but I'm honestly too lazy to set up a benchmark right now to test it, so I can offer no substantial response. faggot.
Name:
Anonymous2007-10-09 16:41
faggot.
Name:
Anonymous2007-10-09 16:42
>>39
faggot, read up on connection pooling, faggot.