Re: [SQL] ERROR: null value in column "id" violates not-null constraint

2009-10-10 Thread Robert Paulsen
On Saturday 10 October 2009 4:12 pm, Tom Lane wrote: > Robert Paulsen writes: > > I do have a question, though, I fixed things as indicated above: > > id integer DEFAULT nextval('vault_id_seq') NOT NULL, > > Dump gave back > > id integer DEFAULT nextval('vault_id_seq'::text) NOT NULL, > >

Re: [SQL] ERROR: null value in column "id" violates not-null constraint

2009-10-10 Thread Tom Lane
Robert Paulsen writes: > I do have a question, though, I fixed things as indicated above: > id integer DEFAULT nextval('vault_id_seq') NOT NULL, > Dump gave back > id integer DEFAULT nextval('vault_id_seq'::text) NOT NULL, > That "text" seems odd. Should I change it? That's all there

Re: [SQL] ERROR: null value in column "id" violates not-null constraint

2009-10-10 Thread Robert Paulsen
On Saturday 10 October 2009 3:16 pm, Tom Lane wrote: > Robert Paulsen writes: > > On Saturday 10 October 2009 2:00 pm, Robert Paulsen wrote: > >> So no default for id. What should it be? > >> default nextval('vault_id_seq') > > > > Should have tried that before posting last message -- it worked. T

Re: [SQL] ERROR: null value in column "id" violates not-null constraint

2009-10-10 Thread Tom Lane
Robert Paulsen writes: > On Saturday 10 October 2009 2:00 pm, Robert Paulsen wrote: >> So no default for id. What should it be? >> default nextval('vault_id_seq') > Should have tried that before posting last message -- it worked. Thanks! So the next question is just what happened and whether you

Re: [SQL] ERROR: null value in column "id" violates not-null constraint

2009-10-10 Thread Robert Paulsen
On Saturday 10 October 2009 2:00 pm, Robert Paulsen wrote: > > So no default for id. What should it be? > > Something like one of this? > > default nextval('vault_id_seq') > Should have tried that before posting last message -- it worked. Thanks! -- Sent via pgsql-sql mailing list (pgsql-s

Re: [SQL] ERROR: null value in column "id" violates not-null constraint

2009-10-10 Thread Robert Paulsen
On Saturday 10 October 2009 1:46 pm, Tom Lane wrote: > Robert Paulsen writes: > > I have a database with a sequence field as a primary key in a table and > > can no longer insert data into it as it gets the subject error message. > > Does the table actually have a default for id anymore? (Try loo

Re: [SQL] ERROR: null value in column "id" violates not-null constraint

2009-10-10 Thread Tom Lane
Robert Paulsen writes: > I have a database with a sequence field as a primary key in a table and can > no > longer insert data into it as it gets the subject error message. Does the table actually have a default for id anymore? (Try looking at it with psql's \d command.) > POSSIBLE REASON FOR

[SQL] ERROR: null value in column "id" violates not-null constraint

2009-10-10 Thread Robert Paulsen
I have a database with a sequence field as a primary key in a table and can no longer insert data into it as it gets the subject error message. This database has been in use for well over two years without any problems using postgresql-server-8.0.13-1.1. Suddenly, when I attempt to add a new re

[SQL] superusuario, auditorías y cambios de c lave

2009-10-10 Thread suso
Hola de nuevo, espero esten bién todos:) Tengo el siguiente sistema: Postgres 8.4, winxp, vb6,tablas de auditoría para cada tabla en cada base de datos, pero en cada base de datos añadí un schema "audit" para crear ahí las tablas de auditorías, cuyo propietario es "auditor", pero evidentemente q