On Thursday 30 Oct 2003 4:53 am, you wrote:
[EMAIL PROTECTED] writes:
Actually PostgreSQL is at par with MySQL when the query is being
Properly Written(simplified)
These are not the same query, though. Your original looks like
Yes that was an optimisation on haste the simplification was
On Thu, Oct 30, 2003 at 01:15:44AM +0530, [EMAIL PROTECTED] wrote:
Actually PostgreSQL is at par with MySQL when the query is being Properly
Written(simplified)
In mysql:
mysql SELECT DISTINCT main.* FROM Groups main join Principals Principals_1
using(id) join ACL
ACL_2 on
So its not just PostgreSQL that is suffering from the bad SQL but MySQL also. But
the
question is my does PostgreSQL suffer so badly ?? I think not all developers write
very nice
SQLs.
Its really sad to see that a fine peice of work (RT) is performing sub-optimal
becoz of
malformed
On Thu, 30 Oct 2003 [EMAIL PROTECTED] wrote:
So its not just PostgreSQL that is suffering from the bad SQL but MySQL also.
But the
question is my does PostgreSQL suffer so badly ?? I think not all developers
write very
nice SQLs.
Its really sad to see that a fine peice of work
[EMAIL PROTECTED] writes:
Actually PostgreSQL is at par with MySQL when the query is being
Properly Written(simplified)
These are not the same query, though. Your original looks like
SELECT DISTINCT main.*
FROM Groups main , Principals Principals_1, ACL ACL_2
WHERE
((ACL_2.RightName =
[EMAIL PROTECTED] writes:
I really not intend to start a flame war here but i am genuinely
seeking help to retain PostgreSQL as my database for my RT system.
If there are things that can be discovered to feed back to the RT
developers to improve PostgreSQL's usefulness as a data store for RT,
Tom Lane [EMAIL PROTECTED] writes:
(I'd argue that the SQL generator is broken anyway ;-) if it generates
such horrible conditions as that. Or maybe the real problem is that
the database schema is a mess and needs rethinking.)
I had the same reaction when I first saw those queries. But I
