On Thursday 30 March 2006 12:07, [EMAIL PROTECTED] wrote: > To many people "SQL" in the name implies "big databases". I know > from personal experience at work. The powers-that-be didn't want > to support another database server (we already have Sybase) and > didn't want our group's experimental data "polluting" the > production database, so the folks who wanted it went the > SQLite/pysqlite route. They were immediately bitten by the > multiple reader/single writer limitation and they tried to cram too > much data into it, so performance further sucked.
And people trying to build production systems on SimpleHTTPServer, SimpleXMLRPCServer, smptd, or dumbdbm will also find their performance sucks. What's your point? Anthony -- Anthony Baxter <[EMAIL PROTECTED]> It's never too late to have a happy childhood. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
