Re: rule system oddity

From: Jaime Casanova <systemguards(at)yahoo(dot)com>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: Bernd Helmle <bernd(dot)helmle(at)oopsware(dot)de>, pgsql hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: rule system oddity
Date: 2005-01-05 16:52:13
Message-ID: 20050105165213.19005.qmail@web50008.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

--- Michael Fuhr <mike(at)fuhr(dot)org> escribió:
> On Tue, Jan 04, 2005 at 11:51:54PM -0600, Jaime
> Casanova wrote:
>
> > create view vfoo as select oid, * from foo;
> > ...
> > create rule insrule as on insert to vfoo
> > do instead
> > insert into foo(id, name) values (new.id,
> new.name);
> > ...
> > insert into vfoo values(1, 'test1');
> > ERROR: invalid input syntax for integer: "test1"
> >
> > it seems like it's trying to insert into the oid
> > column is that the intended behaviour? or is it a
> bug?
> > (i think is the latter).
>
> vfoo has three fields: oid, id, and name. If you
> INSERT without a
> column list, the values are assigned to the columns
> in order: oid=1,
> id='test1', name=NULL. Are you suggesting that the
> insert should
> ignore oid since its source is a system column? I'm
> not sure such
> behavior would be desirable because of the
> inconsistency it would
> introduce: sometimes values would be assigned to the
> displayed
> columns in order, but other times one or more of
> those columns might
> be implicitly skipped.
>
ahhh... you are right i have to use named column list
to do that insert.

regards,
Jaime Casanova

_________________________________________________________
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2005-01-05 18:18:44 Re: [BUGS] More SSL questions..
Previous Message ohp 2005-01-05 15:42:37 Where are the docs