Thanks for reply,
This solution looks promising. I'll look at it and test it and let you know.
Thanks once more
Trigve
- Original Message
From: Richard Huxton <[EMAIL PROTECTED]>
To: Trigve Siver <[EMAIL PROTECTED]>
Sent: Thursday, May 31, 2007 10:33:40 AM
Subjec
just other properties as required (eg highlight them).
Alternatively if you're working with ado you can store the records bookmark in
the tag property. That's particulary handy when you want
to look up information in a recordset when clicking on an item in the listview.
>>>
>- Original Message
>From: Richard Huxton <[EMAIL PROTECTED]>
>To: Trigve Siver <[EMAIL PROTECTED]>
>Cc: pgsql-sql@postgresql.org
>Sent: Wednesday, May 30, 2007 9:05:09 PM
>Subject: Re: [SQL] slow query execution
>
>Trigve Siver wrote:
>>
>&g
>- Original Message
>From: Andrew Sullivan <[EMAIL PROTECTED]>
>To: pgsql-sql@postgresql.org
>Sent: Wednesday, May 30, 2007 8:30:32 PM
>Subject: Re: [SQL] slow query execution
>
>On Wed, May 30, 2007 at 11:08:02AM -0700, Trigve Siver wrote:
>
>> I wan
>- Original Message
>From: Andrew Sullivan <[EMAIL PROTECTED]>
>To: pgsql-sql@postgresql.org
>Sent: Wednesday, May 30, 2007 7:39:18 PM
>Subject: Re: [SQL] slow query execution
>
>On Wed, May 30, 2007 at 10:03:16AM -0700, Trigve Siver wrote:
>> Hi, Thanks f
Thanks a lot
Trigve
- Original Message
From: Rodrigo De León <[EMAIL PROTECTED]>
To: pgsql-sql@postgresql.org; Trigve Siver <[EMAIL PROTECTED]>
Sent: Wednesday, May 30, 2007 7:28:47 PM
Subject: Re: [SQL] slow query execution
On 5/30/07, Trigve Siver <[EMAIL PROTECTED]>
e
to some sources or give me some examples, please?
Thanks
Trigve
- Original Message
From: Andrew Sullivan <[EMAIL PROTECTED]>
To: pgsql-sql@postgresql.org
Sent: Wednesday, May 30, 2007 6:45:53 PM
Subject: Re: [SQL] slow query execution
On Wed, May 30, 2007 at 08:56:45AM -07
Hi all,
This query executes very slow:
select (select count(*) from customer where id <= a.id) as row, id, from
customer as a order by id;
Where customer has id column and others and has also index on id column. The
table has about 10.000+ records. When used with "explain", it gives me this
o
