Hi there,

I found a bug in the export routine in both pgAdminIII V 1.6.1 and 1.6.2
My client WinXp Home SP2 with all patches up to date
My DB pg Ver. 8.1.5 (UTF-8) running on a Linux Box


After issuing a query , it gets, let's say 145 rows.
When creating a HTML-report, all rows appear.
When exporting to a CSV-file, SOME rows are empty ";;;;;;;;" - only
delimiter is there.
In my case the first few rows from grid (five, three - no real rule
there ) were missing,
but the empty lines are allways on the end of the file.

I tried with different encodings, (UTF-8 vs Latin1), rebooting the PC
etc, same Problem.

I downgraded my PC to pgAdmin1.4.3 - no Problem any more


As I saw, other people have problems with the exporter too.
Probably you guys have missed something in the code,
when intoducing that HTML-report stuff - which, BTW I really like.

Thanks and regards
Mathais Durst


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Mathias Durst wrote:
> Hi there,
>
> I found a bug in the export routine in both pgAdminIII V 1.6.1 and 1.6.2
> My client WinXp Home SP2 with all patches up to date
> My DB pg Ver. 8.1.5 (UTF-8) running on a Linux Box
>
>
> After issuing a query , it gets, let's say 145 rows.
> When creating a HTML-report, all rows appear.
> When exporting to a CSV-file, SOME rows are empty ";;;;;;;;" - only
> delimiter is there.
> In my case the first few rows from grid (five, three - no real rule
> there ) were missing,
> but the empty lines are allways on the end of the file.
>
> I tried with different encodings, (UTF-8 vs Latin1), rebooting the PC
> etc, same Problem.
>
> I downgraded my PC to pgAdmin1.4.3 - no Problem any more

Mathias;

This bug was seen during beta by Mike iirc (CC'd), however I thought
we'd cured it. I've had another idea about the possible cause and have
worked up a test build which can be found at
http://developer.pgadmin.org/~dpage/pgAdmin3.zip - please download it
and give it a try.

Mike; this may well cure the other problem you reported - can you test
as well please?

Thanks, Dave

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Mathias Durst wrote:
> Hello Dave,
>
> I downloaded pgAdmin 1.6.2 again (release) - still same Problem
>
> Then I replaced the executable with the one provided in your link -
> Export now OK - great.

Great, thanks for testing. I think it will be more reliable as well, so
I've committed the patch.

> Thanks for your quick response.
>
> OT: the included image shows a cosmetically problem in the German version.
> Since I have a WinXp box I couldn't fix the mo file myself.
> However, it needs to be fixed anyway on the released code.
>
> The line should read: "Die ersten 100 Zeilen anzeigen" - the
> qqqqqqqqqqq are mistakenly there.

Fixing...

Thanks, Dave

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Hello,

I have tried the new exe file and it has fixed my issue as well.

Mike

On Wed, 2007-01-10 at 14:09 +0000, Dave Page wrote:
> Mathias Durst wrote:
> > Hi there,
> >
> > I found a bug in the export routine in both pgAdminIII V 1.6.1 and 1.6.2
> > My client WinXp Home SP2 with all patches up to date
> > My DB pg Ver. 8.1.5 (UTF-8) running on a Linux Box
> >
> >
> > After issuing a query , it gets, let's say 145 rows.
> > When creating a HTML-report, all rows appear.
> > When exporting to a CSV-file, SOME rows are empty ";;;;;;;;" - only
> > delimiter is there.
> > In my case the first few rows from grid (five, three - no real rule
> > there ) were missing,
> > but the empty lines are allways on the end of the file.
> >
> > I tried with different encodings, (UTF-8 vs Latin1), rebooting the PC
> > etc, same Problem.
> >
> > I downgraded my PC to pgAdmin1.4.3 - no Problem any more
>
> Mathias;
>
> This bug was seen during beta by Mike iirc (CC'd), however I thought
> we'd cured it. I've had another idea about the possible cause and have
> worked up a test build which can be found at
> http://developer.pgadmin.org/~dpage/pgAdmin3.zip - please download it
> and give it a try.
>
> Mike; this may well cure the other problem you reported - can you test
> as well please?
>
> Thanks, Dave
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings


---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

mike wrote:
> Hello,
>
> I have tried the new exe file and it has fixed my issue as well.

Excellent - thanks for testing.

Regards, Dave

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate