[pgadmin-support] Serious bug in edit grid?
When editing my table contents multiple rows wiht
the same value all get changed.
Table design:
CREATE TABLE
customer_service_attributes( customer_service_attribute_id int4
NOT NULL DEFAULT
nextval('public.cust_srv_features_customer_service_attributes_seq'::text),
_service_id int4 NOT NULL, -- This can be derrived from the attrib ID, but is
also here to make queries easier. service_attr_id int4 NOT
NULL, _customer_id int4 NOT NULL, customer_service_id int4
NOT NULL, value text NOT NULL, CONSTRAINT
customer_service_attributes_pkey PRIMARY KEY
(customer_service_attribute_id), CONSTRAINT
customer_service_attributes_customer_id_fkey FOREIGN KEY
(_customer_id) REFERENCES customer
(customer_id) MATCH SIMPLE ON UPDATE RESTRICT
ON DELETE RESTRICT, CONSTRAINT
customer_service_attributes_customer_service_id_fkey FOREIGN KEY
(customer_service_id) REFERENCES
customer_services (customer_service_id) MATCH
SIMPLE ON UPDATE RESTRICT ON DELETE
RESTRICT, CONSTRAINT customer_service_attributes_service_attr_id_fkey
FOREIGN KEY (service_attr_id) REFERENCES
service_attribute (service_attr_id) MATCH
SIMPLE ON UPDATE RESTRICT ON DELETE
RESTRICT, CONSTRAINT customer_service_attributes_service_id_fkey
FOREIGN KEY (_service_id) REFERENCES service
(service_id) MATCH SIMPLE ON UPDATE RESTRICT
ON DELETE RESTRICT) WITHOUT OIDS;
When editing the value feild in rows in the grid
changing value x to y, all rows with value x become y. Looking in the query log
shows the following
STATEMENT: UPDATE customer_service_attributes
SET value='y'::pg_catalog.text WHERE value = 'x'::pg_catalog.text
Shouldn't this be refrencing the primary key of
customer_service_attribute_id in the where clause? as in
STATEMENT: UPDATE customer_service_attributes
SET value='y'::pg_catalog.text WHERE customer_service_attribute_id =
620
Am I doing something wrong or is there a
massive bug here??
Please reply or cc to this address, I'm not
subscribed to this list.
Re: [pgadmin-support] Serious bug in edit grid?
Latest stable version of pgadminIII -- 1.4.1
postgresql 8.0.4 running on FreeBSD 5.4 (from ports)
I do not belive I dropped and readded any columns to this table.
customer_service_attribute_id should have been there as a serial from the
start.
---
Another unrelated bug I'll like to bring up. On connect as an admin with the
extensions installed an error is generated regarding /proc/uptime because
freebsd does not by default have a /proc.
Workaround: install procfs or ignore.
proper solution: supress the error or obtain uptime using another method.
- Original Message -
From: "Andreas Pflug" <[EMAIL PROTECTED]>
To: "Chris St Denis" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, January 23, 2006 3:33 PM
Subject: Re: [pgadmin-support] Serious bug in edit grid?
> Chris St Denis wrote:
>
> > When editing my table contents multiple rows wiht the same value all
> > get changed.
> >
> > Table design:
> >
> > CREATE TABLE customer_service_attributes
> > (
> > customer_service_attribute_id int4 NOT NULL DEFAULT
> >
nextval('public.cust_srv_features_customer_service_attributes_seq'::text),
> > _service_id int4 NOT NULL, -- This can be derrived from the attrib
> > ID, but is also here to make queries easier.
> > service_attr_id int4 NOT NULL,
> > _customer_id int4 NOT NULL,
> > customer_service_id int4 NOT NULL,
> > value text NOT NULL,
> > CONSTRAINT customer_service_attributes_pkey PRIMARY KEY
> > (customer_service_attribute_id),
> > CONSTRAINT customer_service_attributes_customer_id_fkey FOREIGN KEY
> > (_customer_id)
> > REFERENCES customer (customer_id) MATCH SIMPLE
> > ON UPDATE RESTRICT ON DELETE RESTRICT,
> > CONSTRAINT customer_service_attributes_customer_service_id_fkey
> > FOREIGN KEY (customer_service_id)
> > REFERENCES customer_services (customer_service_id) MATCH SIMPLE
> > ON UPDATE RESTRICT ON DELETE RESTRICT,
> > CONSTRAINT customer_service_attributes_service_attr_id_fkey FOREIGN
> > KEY (service_attr_id)
> > REFERENCES service_attribute (service_attr_id) MATCH SIMPLE
> > ON UPDATE RESTRICT ON DELETE RESTRICT,
> > CONSTRAINT customer_service_attributes_service_id_fkey FOREIGN KEY
> > (_service_id)
> > REFERENCES service (service_id) MATCH SIMPLE
> > ON UPDATE RESTRICT ON DELETE RESTRICT
> > )
> > WITHOUT OIDS;
> >
> >
> > When editing the value feild in rows in the grid changing value x to
> > y, all rows with value x become y. Looking in the query log shows the
> > following
> >
> > STATEMENT: UPDATE customer_service_attributes SET
> > value='y'::pg_catalog.text WHERE value = 'x'::pg_catalog.text
> >
> > Shouldn't this be refrencing the primary key of
> > customer_service_attribute_id in the where clause? as in
> >
> > STATEMENT: UPDATE customer_service_attributes SET
> > value='y'::pg_catalog.text WHERE customer_service_attribute_id = 620
> >
> >
> > Am I doing something wrong or is there a massive bug here??
>
>
> Which version?
> We had a recent fix that could hit you when you dropped columns and
> readded some as PK.
>
> Regards,
> Andreas
>
>
---(end of broadcast)---
TIP 6: explain analyze is your friend
[pgadmin-support] Replication upgrade fails
I upgraded slony on the servers from 1.2.13 to 1.2.14 and downloaded the 1.2.14 creation scripts to my client. I created the new empty cluster and did a "upgrade node" on the old cluster, selecting the new one from the box. I get "Column not found in pgSet: indname" After dismissing that error dialog I get a second one. 'Error: relation "sl_log_1_idx1" already exists.' What is wrong and how do I fix it? -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
Re: [pgadmin-support] Wish List Request: Tabbed SQL Query Window
Fernando Hevia wrote: On Tue, Jun 24, 2008 at 4:17 AM, Ryan Daniels <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: I would like to request that the SQL query window have tabs so that you can have multiple queries/files open in the same window. Agreed. That would be a nice feature to see in the next release. And also an option/setting to filter server context messages. Doable or not, I want to thank the developers for their great work on this project! Regards, Fernando. I would also like to see a more graceful handling of disconnects. Once of my servers I connect to through a firewall. The firewall connection eventually times out causing a disconnect that pgadmin doesn't handle very happily. Would be nice for it to just reconnect transparently without closing all of the tree, popping up several errors, etc. Or just provide a keep-alive option. -- Chris St Denis Programmer SmarttNet (www.smartt.com) Ph: 604-473-9700 Ext. 200 --- "Smart Internet Solutions For Businesses"
