Re: Edit grid crashes adding new rows to table with autoincrement primary key.
От | Dave Page |
---|---|
Тема | Re: Edit grid crashes adding new rows to table with autoincrement primary key. |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E4011C93E5@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Edit grid crashes adding new rows to table with autoincrement primary key. ("David Nash" <dnash@ideorlando.org>) |
Список | pgadmin-support |
> -----Original Message----- > From: pgadmin-support-owner@postgresql.org > [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of David Nash > Sent: 10 March 2006 14:02 > To: pgadmin-support@postgresql.org > Subject: Re: [pgadmin-support] Edit grid crashes adding new > rows to table with autoincrement primary key. > > >> Interesting. Out of interest (if you still have it), what > does pg_dump > >> think the schema looks like? It sounds like pgAdmin is > misreading the > >> schema somehow, causing the crash - most likely when it > tries to detect > >> the primary key. One thought - in the edit grid, did the > int8 column > >> have [PK] in the column header? > > In fact, the edit grid does show [PK] in the column header -- > it reads: > > heritages_id > [PK] int8 > > ... and here's the output from pg_dump -s -t Heritages : Seems it gets that right then - it would also be interesting to see what query pgAdmin used to do the update if you still have the log around. Thanks, Dave
В списке pgadmin-support по дате отправления: