Thread: possible bug in PG admin
see attached picture.
PGadmin the displayed data is not staying in desired sort order (order by date desc) per the SQL command .... select comment_id , item_id, item_number, item_descrip1, comment_text, comment_date, comment_user
from item, comment
where item_id = comment_source_id and comment_source = 'I'
and item_active and comment_text::char(10) = 'List Price'
and comment_date>= '2015-01-01'
order by comment_date desc
Attachment
pgAdmin4 don't do any sorting by itself, it just displays what it receives from server.
Did you cross verify your output with psql?
I'm not able to re-produce the issue (attaching screenshot).
--
Regards,
On Fri, Mar 16, 2018 at 7:40 PM, Justin <zzzzz.graf@gmail.com> wrote:
Operating System Windows 7 64bitSQL commandThe return set is around 4000 rows long, the two source tables are 14,000 and 251,340 rowssee attached picture.PGadmin the displayed data is not staying in desired sort order (order by date desc) per the SQL command ....
select comment_id , item_id, item_number, item_descrip1, comment_text, comment_date, comment_user
from item, comment
where item_id = comment_source_id and comment_source = 'I'
and item_active and comment_text::char(10) = 'List Price'
and comment_date>= '2015-01-01'
order by comment_date desc
Attachment
++ Adding pgadmin-support
(Please keep the group in the loop)
Oh, you were talking about wrong row count that's a bug and will be taken care in new version.
Please download latest version of pgAdmin4 v3.0 when available (most probably next week) and let us know if issue persists.
--
Regards,
On Sat, Mar 17, 2018 at 1:01 AM, Justin <zzzzz.graf@gmail.com> wrote:
Its an issue at 2000 records see picture, it starts to repeat over and over againOn Fri, Mar 16, 2018 at 3:14 PM, Justin <zzzzz.graf@gmail.com> wrote:I just noticed something after clicking send button.... the dataset should only be 10,000 records, yet PGAdmin 4 just keeps dumping out records its showing 40,000 records?? its appears it goes all wrong at 2,000 record set....On Fri, Mar 16, 2018 at 3:07 PM, Justin <zzzzz.graf@gmail.com> wrote:out of order does not occur until record 2000not with psql but check in pgadmin3 the display was correcttry using this select statement
with dataset as (select * from generate_series(1,10000))
select *, now()::date + (random()*10)::integer from dataset
order by 2 descOn Fri, Mar 16, 2018 at 1:56 PM, Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com> wrote: pgAdmin4 don't do any sorting by itself, it just displays what it receives from server.Did you cross verify your output with psql?I'm not able to re-produce the issue (attaching screenshot).--Regards,On Fri, Mar 16, 2018 at 7:40 PM, Justin <zzzzz.graf@gmail.com> wrote:Operating System Windows 7 64bitSQL commandThe return set is around 4000 rows long, the two source tables are 14,000 and 251,340 rowssee attached picture.PGadmin the displayed data is not staying in desired sort order (order by date desc) per the SQL command ....
select comment_id , item_id, item_number, item_descrip1, comment_text, comment_date, comment_user
from item, comment
where item_id = comment_source_id and comment_source = 'I'
and item_active and comment_text::char(10) = 'List Price'
and comment_date>= '2015-01-01'
order by comment_date desc
