Re: Vote tallying...

On Sat, 19 Jan 2013 00:12:25 -0500, Dennis Lee Bieber wrote: > On Sat, 19 Jan 2013 07:24:40 +1100, Ben Finney > declaimed the following in > gmane.comp.python.general: > > >> * MySQL's development has suffered under Sun, and become virtually >> moribund under Oracle. They operate as a closed

Re: Vote tallying...

On 20/01/13 08:22, Dennis Lee Bieber wrote: On Sat, 19 Jan 2013 22:58:17 +1100, Lie Ryan 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

Re: Vote tallying...

On Sun, Jan 20, 2013 at 4:46 AM, Tim Chase wrote: > Reading the MySQL gotchas and comparing it to the PostgreSQL gotchas, the > MySQL ones scare the pants off my inner DBA, while the PostgreSQL ones are > mostly "if you're running at 6+yr old version of the software, there are > some peculiar beha

Re: Vote tallying...

On 01/18/13 23:19, Dennis Lee Bieber wrote: On Fri, 18 Jan 2013 18:54:32 -0400, Zero Piraeus On 18 January 2013 16:57, Tim Chase wrote: - there are just some serious what-the-heck's in MySQL's handling of some edge cases regarding NULL values and dates (Feb 31st anybody). There's a good com

Re: Vote tallying...

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

Re: Vote tallying...

Chris Angelico, 19.01.2013 03:00: > On Sat, Jan 19, 2013 at 12:25 PM, Kushal Kumaran wrote: >> Chris Angelico writes: >> >>> On Sat, Jan 19, 2013 at 7:24 AM, Ben Finney wrote: * MySQL's development has suffered under Sun, and become virtually moribund under Oracle. They operate as a clo

Re: Vote tallying...

On Sat, Jan 19, 2013 at 12:25 PM, Kushal Kumaran wrote: > Chris Angelico writes: > >> On Sat, Jan 19, 2013 at 7:24 AM, Ben Finney >> wrote: >>> * MySQL's development has suffered under Sun, and become virtually >>> moribund under Oracle. They operate as a closed shop, occasionally >>> tossi

Re: Vote tallying...

Chris Angelico writes: > On Sat, Jan 19, 2013 at 7:24 AM, Ben Finney > wrote: >> * MySQL's development has suffered under Sun, and become virtually >> moribund under Oracle. They operate as a closed shop, occasionally >> tossing GPL-licensed releases over the wall, with very little input >>

Re: Vote tallying...

: On 18 January 2013 16:57, Tim Chase wrote: > > - there are just some serious what-the-heck's in MySQL's handling of some > edge cases regarding NULL values and dates (Feb 31st anybody). There's a > good compilation of them at [1]. > > [1] > http://sql-info.de/mysql/gotchas.html I'm getting th

Re: Vote tallying...

On Sat, Jan 19, 2013 at 7:24 AM, Ben Finney wrote: > * MySQL's development has suffered under Sun, and become virtually > moribund under Oracle. They operate as a closed shop, occasionally > tossing GPL-licensed releases over the wall, with very little input > accepted from the community. I

Re: Vote tallying...

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

Re: Vote tallying...

On 01/18/13 13:26, Kwpolska wrote: On Fri, Jan 18, 2013 at 4:19 PM, Nick Cash wrote: MySQL would certainly be fine, although I always recommend PostgreSQL over it. Bonus question, why? I write only from my personal experience, but the following might be reasons that Nick recommends PostgreS

Re: Vote tallying...

Kwpolska writes: > On Fri, Jan 18, 2013 at 4:19 PM, Nick Cash > wrote: > > MySQL would certainly be fine, although I always recommend > > PostgreSQL over it. > Bonus question, why? The PostgreSQL community gets asked this question so often that they have a page with resources answering in vario

Re: Vote tallying...

On Fri, Jan 18, 2013 at 4:19 PM, Nick Cash wrote: > MySQL would certainly be fine, although I always recommend PostgreSQL over it. Bonus question, why? -- Kwpolska | GPG KEY: 5EAAEA16 stop html mail| always bottom-post http://asciiribbon.org| http://ca

RE: Vote tallying...

> I have a problem which may fit in a mysql database, but which I only > have python as an alternate tool to solve... so I'd like to hear some > opinions... Is there a reason you can't use an RDBMS for this? MySQL would certainly be fine, although I always recommend PostgreSQL over it. Based on t

Re: Vote tallying...

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? > b

Re: Vote tallying...

On 18/01/13 10:59, Andrew Robinson wrote: Hi, I have a problem which may fit in a mysql database, but which I only have python as an alternate tool to solve... so I'd like to hear some opinions... Since you have a large dataset, you might want to use sqlite3 (http://docs.python.org/2.5/lib/mo

Vote tallying...

Hi, I have a problem which may fit in a mysql database, but which I only have python as an alternate tool to solve... so I'd like to hear some opinions... I'm building a experimental content management program on a standard Linux Web server. And I'm needing to keep track of archived votes an