Re: clone_schema function

From: Igor Neyman <ineyman(at)perceptron(dot)com>
To: Melvin Davidson <melvin6925(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Cc: Daniel Verite <daniel(at)manitou-mail(dot)org>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: clone_schema function
Date: 2015-09-15 13:39:12
Message-ID: A76B25F2823E954C9E45E32FA49D70ECCD516009@mail.corp.perceptron.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I still do not see any problem. The whole purpose of the function is to copy ALL sequences , tables and functions to "new" schema, so new.old WILL exist.

I don't see how you can possibly write a function that references a schema that does not yet exist!

Again, please provide a _working_ example of what you think the problem is.

Melvin,

This statement:

SELECT old.field FROM old.old;

selects column “field” from table “old” which is in schema “old”.

Your script converts it into:

SELECT new.field FROM new.old

which will try to select column “field” from table “new” in schema “new”.
The obvious problem is that there is no table “new” in schema “new”, the table will still be called “old”.

Jim’s example is very similar to what I provided a few days ago.

Regards,
Igor Neyman

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Melvin Davidson 2015-09-15 13:44:30 Re: clone_schema function
Previous Message Melvin Davidson 2015-09-15 13:28:48 Re: clone_schema function