Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Well, how would you define CREATE OR REPLACE TABLE? I think that
> doesn't make much sense, which is why I think CREATE IF NOT EXISTS is
> a reasonable approach.
<hand waving time>
The behavior I'd like to have would be to allow me to give a SELECT
query to run for replacing what is there if there's something. If the
query can not be run on the existing data set, error out of course.
So you know the state for sure after the command, but it depends on your
query being correct. And you can (de)normalize existing data using joins.
The REPLACE keyword would here mean that there's a CTAS going under the
hood, then we add the constraints and indexes and triggers etc. That
would mean being able to express those entities changes too, but it
Well, that may be not precise enough as a spec, but at least that's food
for though I hope.
In response to
pgsql-hackers by date
|Next:||From: Heikki Linnakangas||Date: 2010-04-28 17:44:43|
|Subject: Re: pg_start_backup and pg_stop_backup Re: Re: [COMMITTERS]
pgsql: Make CheckRequiredParameterValues() depend upon correct|
|Previous:||From: Kjell Rune Skaaraas||Date: 2010-04-28 17:32:50|
|Subject: Re: Add column if not exists (CINE)|