Re: Possible Bug in "View data for selected
От | Stijn Vanroye |
---|---|
Тема | Re: Possible Bug in "View data for selected |
Дата | |
Msg-id | edhi22$2eef$1@news.hub.org обсуждение исходный текст |
Ответ на | Re: Possible Bug in "View data for selected ("Dave Page" <dpage@vale-housing.co.uk>) |
Список | pgadmin-hackers |
Dave Page schreef: > > >> -----Original Message----- >> From: pgadmin-hackers-owner@postgresql.org >> [mailto:pgadmin-hackers-owner@postgresql.org] On Behalf Of >> Stijn Vanroye >> Sent: 04 September 2006 08:15 >> To: Dave Page; pgadmin-hackers@postgresql.org >> Subject: Re: [pgadmin-hackers] Possible Bug in "View data for selected >> >> CREATE TABLE casemanager >> ( >> naam varchar(50), >> telefoon varchar(15), >> mobiel varchar(15), >> email varchar(50), >> casemanager_id serial NOT NULL, >> CONSTRAINT pk_casemanager_id PRIMARY KEY (casemanager_id) >> ) >> WITHOUT OIDS; >> ALTER TABLE casemanager OWNER TO someuser; > > I cannot reproduce any failures with this table in SVN trunk code. If > you recreate an empty copy of the table (with a different name, or in a > different DB), does that work as expected? Indeed, if I recreate the table in a different database everything works OK. Strange... The casemanager_id field first was a normal int4 field, but is later dropped and made again as a serial field. That's the only strange thing that happend. No Foreign keys are declared, just 4 simple tables with 1 id of type serial each. I think that I'll recreate the entire and insert the data again. I think that's the easiest way to solve the problem for me. If you wich to persue this a bit further though, let me know I'll be honored to help. I don't know if there are any usefull logs I can enable or something. Regards, Stijn.
В списке pgadmin-hackers по дате отправления: