Belbin, Peter wrote:
Cool. Thank you for fixing it.
Will the next packaged release candidate be any time soon?
There might not be another RC - we're getting dangerously close to
PostgreSQL 8.2 release time and we have to be ready by then. Expect
something within the week though I would thin
Title: RE: [pgadmin-support] bug in 1.6 rc1
Cool. Thank you for fixing it.
Will the next packaged release candidate be any time soon?
-Original Message-
From: Dave Page [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 06, 2006 3:43 PM
To: Belbin, Peter
Cc: 'pgadmin-su
Belbin, Peter wrote:
Here is a table def:
CREATE TABLE st_txn
(
txnid varchar(40),
txnorder varchar(10) NOT NULL,
txnstage varchar(10) NOT NULL,
txnseq varchar(10),
verb varchar(40),
payload varchar(65000),
status varchar(10),
agent varchar(60),
id serial NOT NULL,
CONSTRAINT
Title: RE: [pgadmin-support] bug in 1.6 rc1
Here is a table def:
CREATE TABLE st_txn
(
txnid varchar(40),
txnorder varchar(10) NOT NULL,
txnstage varchar(10) NOT NULL,
txnseq varchar(10),
verb varchar(40),
payload varchar(65000),
status varchar(10),
agent varchar(60),
id
Belbin, Peter wrote:
Seems that the closing quote is missing, along with a bunch of the
previously existing column data.
This appears to be the relevant portion:
2006-11-06 09:25:46 QUERY : Scalar query (byoslab2:5432): SELECT
version();
2006-11-06 09:25:46 QUERY : Query result: PostgreSQL
Title: RE: [pgadmin-support] bug in 1.6 rc1
Seems that the closing quote is missing, along with a bunch of the previously existing column data.
This appears to be the relevant portion:
2006-11-06 09:25:46 QUERY : Scalar query (byoslab2:5432): SELECT version();
2006-11-06 09:25:46 QUERY
Belbin, Peter wrote:
a)
I'm using the windows version of the latest 1.6rc1 release of
pgAdmin-III, and have a consistently reproducible error.
Here are the steps to reproduce it:
After selecting a table, and using the context (right-click-popup) menu
and choosing 'View Data->View
a)
I'm using the windows version of the latest 1.6rc1
release of pgAdmin-III, and have a consistently reproducible error.
Here are the steps to reproduce it:
After selecting a table, and using the context
(right-click-popup) menu and choosing 'View Data->View All Rows'
to get th
