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.
Th
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
Dave Page a ecrit le 10/01/2007 10:56:
Laurent ROCHE wrote:
But the problem is that using pg_dump does not produce the same file format
than PG Admin (re: SERIAL, see on of my previous post). So you are using the
pg_dump routine when I use the command line: it's different anyway with
differen
Hurrah !
End of a long story !
I should have read the messages from the backup dialog more carefully, and I
would have seen the pg_dump command !
And I would have noticed that PG Admin uses its own pg_dump.
So my problems (using pg_dump v8.2 instead of PG Admin: SERIAL replaced by INT
and SEQ
Laurent ROCHE wrote:
> Hi,
>
> But the problem is that using pg_dump does not produce the same file format
> than PG Admin (re: SERIAL, see on of my previous post). So you are using the
> pg_dump routine when I use the command line: it's different anyway with
> different options.
>
How can it
Hi,
But the problem is that using pg_dump does not produce the same file format
than PG Admin (re: SERIAL, see on of my previous post). So you are using the
pg_dump routine when I use the command line: it's different anyway with
different options.
Have fun,
[EMAIL PROTECTED]
The Computing Fr
Laurent ROCHE wrote:
> Well, something changed between the two versions ... as I don't get the file
> in the same format I used to have.
The only thing that's changed in the backup code since 1.6.0 is the
copyright comment and a line of code to center the dialogue over it's
parent.
The culprit i
Hello,
i think there are 2 bugs in pgadmin:
CREATE TABLE test_bit
(
id text NOT NULL,
byte bit(8) NOT NULL,
CONSTRAINT test_bit_pkey PRIMARY KEY (id)
)
WITHOUT OIDS;
ALTER TABLE test_bit OWNER TO assux;
Insert with pgadmin:
hello,10101010
German error: Länge der Bitkette 1 stimmt nicht mit
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 expo
