From: | "codeWarrior" <gpatnude(at)hotmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: insert on duplicate update? |
Date: | 2005-11-09 16:08:42 |
Message-ID: | dkt6p0$2kpk$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
You absolutely should NOT I repeat NOT -- DON'T dink around with the system
catalogs in ANY database... If you need to create UDT's then you should
follow the proper mechanisms to create your own user-defined types...
""Peter Filipov"" <pfilipov(at)netissat(dot)bg> wrote in message
news:opszy0zlg8ligf9v(at)draco(dot)(dot)(dot)
> hi,
> is there in postgres anything similar to:
> insert .... on duplicate update?
> here is the problem i need a solution for:
> I need to insert in pg_type a row which was previously selected from there
> and
> with slight modifications, the problem is that when i try to insert the
> row
> there might be a row with the same 'typname' which is sort of primary key.
> The second problem is that when doing those operations i don't want to
> depend
> on the specific structure of the pg_type catalog. I want my procedure
> to work even if in some future release additional columns to pg_type are
> added.
> So what i want is to insert a row in a table that was previously selected
> from the same
> table but if there is primary key collision i want to update the row that
> collided. And
> all these without being dependant on the table structure.
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
From | Date | Subject | |
---|---|---|---|
Next Message | TJ O'Donnell | 2005-11-09 16:13:56 | Re: resetting superuser password |
Previous Message | Tom Lane | 2005-11-09 16:07:56 | Re: psql scripts |