Re: 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 : Query result: PostgreSQL 8.1.4 on
sparc-sun-solaris2.9, compiled by GCC gcc (GCC) 3.3.2
2006-11-06 09:25:46 QUERY : Void query (byoslab2:5432): UPDATE st_txn SET
payload='<vsr><result><sbcs><sbc id="1"><sbcElement /><sbcName /><sbcName
/><ip /></sbc><sbc id="2"><sbcElement /><sbcName /><sbcName /><ip
/></sbc><sbcMarket
/></sbcs><options><vpn_id>22222</vpn_id><dhcp_by>zzzz</dhcp_by><ip_helper_re
q>N/A</ip_helper_req><network_sec_int>FALSE</network_sec_int><default_gw_loc
>No</default_gw_loc></options><ipspaces><subnet><circuitid>4444444</circuiti
d><ipaddress>10.0.1.1</ipaddress><network>10.0.1.0/24</network><default_rout
er>10.0.1.1</default_router><primary_dns>10.0.0.5</primary_dns><secondary_dn
s>10.0.0.6</secondary_dns><cpe_primary_dns>111.222.333.2</cpe_primary_dns><c
pe_secondary_dns>333.333.333.33</cpe_secondary_dns><domain_name
/><ip_helper_primary /><ip_helper_secondary /><ip_route
/><vpn_sbc_static_route_1 /><vpn_sbc_static_route_2
/><wancpeip>88.888.888.88</wancpeip><LanStaticPool start="10.0.1.2"
stop="10.0.1.100" /><LanDhcpPool start="10.0.1.101" stop="10.0.1.254"
/><wanaggip>63.252.159.97</wanaggip><wannetwork>63.2
2006-11-06 09:25:46 ERROR : ERROR: syntax error at end of input at
character 2130

-----Original Message-----
From: Dave Page [mailto:dpage(at)postgresql(dot)org]
Sent: Saturday, November 04, 2006 10:45 AM
To: Belbin, Peter
Cc: 'pgadmin-support(at)postgresql(dot)org'
Subject: Re: [pgadmin-support] bug in 1.6 rc1

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 All Rows' to get the Edit Data window,
> then selecting row and column defined as 'character varying(65000)', and
> editing the contained xml, moving away (clicking on another row)
> produces the following error message:
>

Can you enable query logging on your server and see what is actually
being sent to the server please?

>
> Subsequent attempts to move to another row produces a dialog box
> querying whether I want to save changes, which leads to another of the
> above messages appearing.
>
>
> Ie: it enters some sort of loop where it knows data has not been saved,
> but errors out when trying to save it, which sets it up for another
> iteration of the error cycle.
>

That's intended - it's so you don't lose the text you might have just
spend five minutes typing in (which can be annoying if the error was
caused by a simple constraint error for example. To get out of the loop,
after you see the error either fix it, or hit the undo button to revert
the changes you've made.

>
>
> I rather like the ability to just bring up the entire table with a
> single click rather than continually having to navigate into the
> sub-menu of the context menu that appears when you're on a table / view
> type object in the hierarchy on the left.
>
>
>
> Is there a way to customize the context menu so that the 'favourite'
> edit window option can be moved to the top layer of the context menu to
> save having to continually navigate into the sub-menu?
>
>
>
> This would be a nice customization capability if it's not already
> there..... if it is already there, do tell.

No, this is not currently possible on the context menu, but you can just
hit the button on the toolbar.

Regards, Dave

NOTICE: This electronic mail transmission may contain confidential
information and is intended only for the person(s) named. Any use, copying
or disclosure by any other person is strictly prohibited. If you have
received this transmission in error, please notify the sender via e-mail.