Re: Postgresql v MySQL

2009-02-08 Thread richr
Barry Pederson has nice, short example of adding PostgreSQL full text search to an existing Djanog app at: http://barryp.org/blog/entries/postgresql-full-text-search-django/ On Feb 8, 11:22 am, Alex Gaynor wrote: > On Sun, Feb 8, 2009 at 11:20 AM, Petite Abeille > wrote: > > > > > > > > >

Re: Postgresql v MySQL

2009-02-08 Thread AmanKow
I started with mysql and moved to postgres. My main reasons: 1) If you ever need to dumpdata/loaddata, you may find that postgres (correctly) defers checking of fk constraints until after the a transaction is complete. MySQL checks the constraints as each record is added, even inside of a trans

Re: Postgresql v MySQL

2009-02-08 Thread Justin Bronn
On Feb 7, 8:06 am, Tim Chase wrote: > PostgreSQL has built-in GIS data-types and functions, which I > believe are required for theGeoDjangofunctionality (or Oracle). >   PG also allows flexible creation of new data-types and > functions/operators as shown by the GIS data-types that were > integra

Re: Postgresql v MySQL

2009-02-08 Thread Alex Gaynor
On Sun, Feb 8, 2009 at 11:20 AM, Petite Abeille wrote: > > > On Feb 8, 2009, at 5:17 PM, Peter2108 wrote: > > > Thanks. Between posting and your response I found out that MySQL > > has built in support for full-text searchs but PostgreSQL does not. > > Hmmm... > > http://www.postgresql.org/docs/8.

Re: Postgresql v MySQL

2009-02-08 Thread Petite Abeille
On Feb 8, 2009, at 5:17 PM, Peter2108 wrote: > Thanks. Between posting and your response I found out that MySQL > has built in support for full-text searchs but PostgreSQL does not. Hmmm... http://www.postgresql.org/docs/8.3/static/textsearch.html -- PA. http://alt.textdrive.com/nanoki/ --~

Re: Postgresql v MySQL

2009-02-08 Thread Peter2108
Thanks. Between posting and your response I found out that MySQL has built in support for full-text searchs but PostgreSQL does not. But Django seems as happy with the one as the other. -- Peter On Feb 7, 2:06 pm, Tim Chase wrote: > > Is there any clear reason for preferring one of these DBMS o

Re: Postgresql v MySQL

2009-02-07 Thread Tim Chase
> Is there any clear reason for preferring one of these DBMS over the > other for use with Django (1.0 onwards). Historically, PostgreSQL has favored correctness, ANSI standards, and data-integrity while MySQL has favored speed and pluggability. For the most part, they've reached equilibrium.