On 7/24/07, Andreas Ahlenstorf <[EMAIL PROTECTED]> wrote:
>
> Am 24.07.2007 um 04:43 schrieb Kenneth Gonsalves:
>
> > The current versions of those manuals do not seem to
> > have those sections any more - so how can you trust a group that is
> > rewriting it's history?
>
> You're always right and
Am 24.07.2007 um 04:43 schrieb Kenneth Gonsalves:
> The current versions of those manuals do not seem to
> have those sections any more - so how can you trust a group that is
> rewriting it's history?
You're always right and never wrong, eh?
Sorry, but such statements as yours are plain FUD. M
On 22-Jul-07, at 11:33 AM, Nicola Larosa wrote:
>> I think it's this historical baggage of non-ANSI-compliance for MySQL
>> that dings it to a lower status than PostgreSQL. As the newer, more
>> compliant versions of MySQL begin to be more available on hosting
>> services, this gap will close.
Tim Chase wrote:
> I think it's this historical baggage of non-ANSI-compliance for MySQL
> that dings it to a lower status than PostgreSQL. As the newer, more
> compliant versions of MySQL begin to be more available on hosting
> services, this gap will close.
MySQL developers made many wrong c
walterbyrd wrote:
> I know that PostgreSQL is recommended, but why? Are the django
> developers assuming a high-traffic, database intensive site.
Not necessarily. Using a separate server, instead of an embedded one, you
pay a small setup cost once, and then reap benefits all the time.
> Are th
On 21 juil, 01:14, "Joe Bloggs" <[EMAIL PROTECTED]> wrote:
>
> MySQL accepts the date 31st February 2007 and has several other lax views of
> rounding data or squeezing it in when it should reject it.
SQLite has this problem as well, being untyped and effectively
coercing everything to
strings un
On Jul 20, 10:50 pm, walterbyrd <[EMAIL PROTECTED]> wrote:
> I know that PostgreSQL is recommended, but why? Are the django
> developers assuming a high-traffic, database intensive site. Are the
> django developers assuming that you will not be using shared hosting?
> I seems to me, that if you a
PostgreSQL scales better with more users
http://tweakers.net/reviews/649/7
MySQL accepts the date 31st February 2007 and has several other lax views of
rounding data or squeezing it in when it should reject it.
http://safari.oreilly.com/0596002114/msql2-CHP-16-SECT-3
MySQL only supports transac
I have had some really annoying performance problems with sqlite
concerning multiple joins partially over views.
The query optimizer did not do his job there and switching two joins
brought a performance boost of several orders of magnitude. This is
actually a thing that is hard to do with django
> I know that PostgreSQL is recommended, but why? Are the django
> developers assuming a high-traffic, database intensive site. Are the
> django developers assuming that you will not be using shared hosting?
Any of the big three (PostgreSQL, MySQL, and sqlite) are quite
well supported in Django.
I know that PostgreSQL is recommended, but why? Are the django
developers assuming a high-traffic, database intensive site. Are the
django developers assuming that you will not be using shared hosting?
I seems to me, that if you are using shared hosting, and if your
database needs are modest, Sql
11 matches
Mail list logo