Re: Bug on the beta release: table cell editor

Just a thought.. Are you leaving the cell (cursor being moved to a
different cell) in order to commit the change before you refresh the table?

Derrick

Olivier Bouiron wrote:
> Hi.
> This is one of the table that I use, and I have the problem with it too.
> But as I said to Hiroshi Saito, I use the beta 1, I've just seen few
> minutes ago that the beta 2 was released.
> I have the problem evry time for the last value that i change.
> I've tested again to use the refresh buton and the new value disepear
> and the old value takes the place.
>
> -- Table: dsi.dsi_pha_ucd
>
> -- DROP TABLE dsi.dsi_pha_ucd;
>
> CREATE TABLE dsi.dsi_pha_ucd
> (
> idspecialite integer NOT NULL,
> code text,
> libelle text NOT NULL,
> idforme integer NOT NULL,
> quantite integer NOT NULL DEFAULT 1,
> volume real DEFAULT -1,
> dosage real NOT NULL DEFAULT 0,
> visible boolean NOT NULL DEFAULT true,
> id integer NOT NULL DEFAULT nextval('dsi_pha_ucd_id_seq'::regclass),
> oldidpres integer,
> oldidprod integer,
> CONSTRAINT dsi_pha_ucd_pkey PRIMARY KEY (id)
> )
> WITH OIDS;
> ALTER TABLE dsi.dsi_pha_ucd OWNER TO postgres;
> GRANT ALL ON TABLE dsi.dsi_pha_ucd TO postgres;
> GRANT ALL ON TABLE dsi.dsi_pha_ucd TO infocentre WITH GRANT OPTION;
>
>
> -- Index: dsi.index_dsi_pha_spe_code
>
> -- DROP INDEX dsi.index_dsi_pha_spe_code;
>
> CREATE INDEX index_dsi_pha_spe_code
> ON dsi.dsi_pha_ucd
> USING btree
> (code);
>
> -- Index: dsi.index_dsi_pha_ucd
>
> -- DROP INDEX dsi.index_dsi_pha_ucd;
>
> CREATE INDEX index_dsi_pha_ucd
> ON dsi.dsi_pha_ucd
> USING btree
> (idspecialite);
>
> Regards,
>
> Olivier Bouiron
> Institut Sainte Catherine
> AVIGNON
>
> Tél: 04 90 27 57 43
>
>
>
> Dave Page a écrit :
>> Olivier Bouiron wrote:
>>
>>> Hi.
>>> I'm using the pgAdmin 1.8 beta release and i've found a bug.
>>> When i use the graphical editor in order to change some values on a
>>> table, evry time, the last value that i change is not saved, and i'm
>>> sure that the edition of the cell stopped.
>>> I don't kow if you have seen this problem...
>>> I'm using pgAdmin on Window XP SP2, and my data base is a postgres 8.1
>>> running on a linux Fedora OS.
>>>
>>
>> I cannot reproduce any issue along these lines. Can anyone else?
>>
>> Regards, Dave
>>
>>
>>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
>
>