Then wouldn't it be more appropriate to ask:
What's the status of the things listed on the PostgreSQL gotchas.
Are they bugs? Are they valid? Have the been resolved? What does
the community thing of those gotchas?
I personally don't take an open ended question like "URL: Any
comments?" as trying to be productive. But I could also just be
burnt out on the whole PgSQL vs MySQL flame war or reading too much
into what I appraised to be terse email. If so I apologize.
Regards,
Gavin
On Oct 6, 2005, at 12:01 PM, Aly S.P Dharshi wrote:
> No flamewar here, I am just trying to see if opinions of others on
> this, as Jim had posted a MySQL one, and that there was a
> PostgreSQL one, so I wanted to see if these are valid, if they
> aren't then that site should be updated to reflect this.
>
> Cheers,
>
> Aly.
>
> On Thu, 6 Oct 2005, Gavin M. Roy wrote:
>
>
>> This sure sounds like a flamewar bait email?
>>
>> On Oct 6, 2005, at 11:07 AM, Aly S.P Dharshi wrote:
>>
>>
>>> http://sql-info.de/postgresql/postgres-gotchas.html
>>> Any comments from folks on the list ?
>>> Cheers,
>>> Aly.
>>> -- Aly S.P Dharshi
>>> aly.dharshi@telus.net
>>>
>>> "A good speech is like a good dress
>>> that's short enough to be interesting
>>> and long enough to cover the subject"
>>> ---------------------------(end of
>>> broadcast)---------------------------
>>> TIP 9: In versions below 8.0, the planner will ignore your desire to
>>> choose an index scan if your joining column's datatypes do not
>>> match
>>>
>>
>> Gavin M. Roy
>> 800 Pound Gorilla
>> gmr@ehpg.net
>>
>>
>>
>
> --
> Aly S.P Dharshi
> aly.dharshi@telus.net
>
> "A good speech is like a good dress
> that's short enough to be interesting
> and long enough to cover the subject"
>
