Edit grid crashes adding new rows to table with autoincrement primary key.
От | David Nash |
---|---|
Тема | Edit grid crashes adding new rows to table with autoincrement primary key. |
Дата | |
Msg-id | 000601c64387$2bff10a0$7f7b0a0a@Dnash обсуждение исходный текст |
Список | pgadmin-support |
Dear friends, I'm seeing a problem consistently when using the edit grid to add new rows to a table whose primary key has data type "bigserial." After completion of editing the columns excluding that of the primary key, when I exit the editing widget (e.g. by pressing the Enter key, or clicking the "Save the changed row" button), the program ends immediately with a message from the operating system that says, "pgAdmin3.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created." Restarting pgAdmin and viewing the same table in the grid shows that the row actually did get inserted prior to the crash. I get the same result if I enter unique data in the primary key column. Editing a table whose primary key is just plain old int2 does not manifest the crash. I've been able to repeat the error as described above many times. My system data is shown below. Many thanks for any suggestions, Dave OS: Win2K with SP4 PostgreSQL version 8.1.3 pgAdmin III versions 1.4.1 and 1.4.2 (error is reproduced in both versions) Table definition: CREATE TABLE "Heritages" ( heritage varchar(30) NOT NULL, heritages_id int8 NOT NULL DEFAULT nextval('"Heritages_heritages_id_seq"'::regclass), CONSTRAINT "Heritages_pkey" PRIMARY KEY (heritages_id) ) WITHOUT OIDS; ALTER TABLE "Heritages" OWNER TO postgres; -- David A. Nash, Ph.D. OneSAF Architecture and Integration (SAIC) (321) 235-7735 (Voice) (321) 235-1606 (Fax) david.a.nash@saic.com
В списке pgadmin-support по дате отправления: