On Thu, May 15, 2008 at 1:59 PM, Szaijan <[EMAIL PROTECTED]> wrote:
> Hi, I developed my first Django app on my Macbook Pro using PostgreSQL
> and
> have recently moved it to a production site which uses MySQL.
> PostgreSQL stores boolean values as True and False, just like Python
> and JS, while
Hi, I developed my first Django app on my Macbook Pro using PostgreSQL
and
have recently moved it to a production site which uses MySQL.
PostgreSQL stores boolean values as True and False, just like Python
and JS, while MySQL uses 1 and 0.
Is there some automated way to get the models to understa
> One of the big advantages of MySQL is ease of use and a choice when it comes
> to how you store data. For example: if you need fast reads and less updates,
> make your table MyISAM (you can even compress it making it smaller and
> faster!). If you need high availability of your data, you can
On 08-Jul-06, at 3:56 AM, Ian Holsman wrote:
> guys...
> this is turning into a religious debate.
given the nature of the question, it was inevitable, but i agree we
could stop here
--
regards
kg
http://lawgon.livejournal.com
http://avsap.org.in
--~--~-~--~~~
guys...
this is turning into a religious debate.
I think the question has been answered.
both are excellent choices.
and in the hands of an expert can be made to shine.
On 08/07/2006, at 8:18 AM, Geert Vanderkelen wrote:
>
> Don Arbow wrote:
>> On Jul 7, 2006, at 3:35 AM, Kenneth Gonsalves wro
Don Arbow wrote:
> On Jul 7, 2006, at 3:35 AM, Kenneth Gonsalves wrote:
>> another thing, your have to be careful about postgresql is that data
>> recovery tools for a borked db for postgres are rare to the point of
>> non-existence, whereas there are lots of them for mysql
>
>
> Perhaps MySQL b
On Jul 7, 2006, at 3:35 AM, Kenneth Gonsalves wrote:
>
> another thing, your have to be careful about postgresql is that data
> recovery tools for a borked db for postgres are rare to the point of
> non-existence, whereas there are lots of them for mysql
Perhaps MySQL borks its databases much mo
On Fri, 2006-07-07 at 14:38 +0200, Geert Vanderkelen wrote:
> Malcolm Tredinnick wrote:
> > I would add, for most projects, it's not a really clear cut case. Django
> > hides the SQL oddities for you, so there's not going to much difference
> > there (using MySQL 5 with transaction support is ki
Hi James, Thomas,
James Bennett wrote:
> On 7/7/06, Thomas Ashelford <[EMAIL PROTECTED]> wrote:
>> I keep reading that PostgreSQL is the preferred database for use with
>> Django, but I'm wondering if anyone can explain what its concrete
>> advantages are.
>
> The advantages of Postgres are most
Hi Malcolm, Tomas,
Malcolm Tredinnick wrote:
> Hi Thomas,
>
> On Thu, 2006-07-06 at 23:17 -0700, Thomas Ashelford wrote:
>> I keep reading that PostgreSQL is the preferred database for use with
>> Django, but I'm wondering if anyone can explain what its concrete
>> advantages are.
I go also wit
On 07-Jul-06, at 3:18 PM, Malcolm Tredinnick wrote:
> I would say "pick on" and if your experience over time suggests
> that the
> database is a problem and tests with the alternative work better, then
> it's not even *that* painful to move data between the two systems.
> They
> both basical
Hi Thomas,
On Thu, 2006-07-06 at 23:17 -0700, Thomas Ashelford wrote:
> I keep reading that PostgreSQL is the preferred database for use with
> Django, but I'm wondering if anyone can explain what its concrete
> advantages are.
>
> I've just moved from DreamHost to Webfaction to get the advantag
On 7/7/06, Thomas Ashelford <[EMAIL PROTECTED]> wrote:
> I keep reading that PostgreSQL is the preferred database for use with
> Django, but I'm wondering if anyone can explain what its concrete
> advantages are.
The advantages of Postgres are mostly to do with its better support of
SQL (you have
Thomas Ashelford wrote:
> So far I can only see a potential negative - I
> may want to use fulltext indexing in the future, and I believe this is
> not available on PostgreSQL.
Look into TSearch2 for full text search in PG
Lorenzo
--~--~-~--~~~---~--~~
You rece
I've been using mysql with Django for about a 8 months and have never
had any issues with it.
I chose mysql as I am more familiar with it. others are more familiar
with postgreSQL.
choose the one you are more comfortable with.
regards
ian.
On 07/07/2006, at 4:17 PM, Thomas Ashelford wrote:
I keep reading that PostgreSQL is the preferred database for use with
Django, but I'm wondering if anyone can explain what its concrete
advantages are.
I've just moved from DreamHost to Webfaction to get the advantage of
using mod_python instead of fcgi. Already the advantages of mod_python
are c
16 matches
Mail list logo
