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
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 simplifica
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
[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,
<[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 =
> 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 s
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
>> 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
>
>
>
> 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
> 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 S
Actually PostgreSQL is at par with MySQL when the query is being Properly
Written(simplified)
like below
rt3=# SELECT DISTINCT main.* FROM Groups main join Principals Principals_1
using(id) join ACL
ACL_2 on (ACL_2.PrincipalId = Principals_1.id) WHERE ((ACL_2.RightName =
'OwnTicket')OR
Dear PostgreSQL gurus,
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.
Few months back i had posted regarding lowering of column names in SQL
being passed to RDBMS by DBIx::SearchBuilder , looks like it was contr
12 matches
Mail list logo
