Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #37083
| From | Lie Ryan <lie.1296@gmail.com> |
|---|---|
| Subject | Re: Vote tallying... |
| Date | 2013-01-19 22:58 +1100 |
| References | <50F8906D.9040203@r3dsolutions.com> <kdb27d$udr$1@ger.gmane.org> <50F9518E.3040509@r3dsolutions.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.689.1358596713.2939.python-list@python.org> (permalink) |
On 19/01/13 00:43, Andrew Robinson wrote: > On 01/18/2013 08:47 AM, Stefan Behnel wrote: >> Andrew Robinson, 18.01.2013 00:59: >>> I have a problem which may fit in a mysql database >> Everything fits in a MySQL database - not a reason to use it, though. >> Py2.5 >> and later ship with sqlite3 and if you go for an external database, >> why use >> MySQL if you can have PostgreSQL for the same price? > MySQL is provided by the present server host. It's pretty standard at > web hosting sites. > It works through "import MySQLdb" -- and it means an IP call for every > action... That is not quite true. With most client libraries, including MySQLdb, connection to localhost goes through a local unix socket (or named pipe in Windows) instead of the TCP stack. > But > it wants to lock the entire database against reads as well as writes > when any access of the database happens. Which is bad... Which is the same restriction as when using XML/JSON. What it means by locking the entire database is that an sqlite database can only be read/written by a single program at any moment in time. For batch processing, locking the entire database is never going to be a problem; for CGI scripts (and their variants), it may be a performance bottleneck for extremely high volume websites.
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Vote tallying... Lie Ryan <lie.1296@gmail.com> - 2013-01-19 22:58 +1100
csiph-web