Re: How to correct schema-names within function when the schema gets renamed?
От | Merlin Moncure |
---|---|
Тема | Re: How to correct schema-names within function when the schema gets renamed? |
Дата | |
Msg-id | CAHyXU0y-MxzCKFunwBs6-8smDidTRKUA2F6=eTi02TSy_FZc7w@mail.gmail.com обсуждение исходный текст |
Ответ на | How to correct schema-names within function when the schema gets renamed? (Andreas <maps.on@gmx.net>) |
Список | pgsql-novice |
On Mon, Aug 29, 2011 at 6:44 AM, Andreas <maps.on@gmx.net> wrote: > Hi, > how can I correct schema-names within function when the schema gets renamed? > PG corrects automagicaly every view and foreign key. > > Though I found that it doesn't update the schema-name in sql-functions. > Say there where a table "bar" in the schema "foo" > and there is a function f(int) that results to "select * from foo.bar where > id = $1". > > Then I rename "foo" to "sansi" and all seems nice till I call f(). > Now I get an error that schema "foo" can't be found. > > How could I find all functions that use the now uncorrect schema-name? > > Btw, server is PG 8.4. IMO, the 'right' way to do functions, especially if you have a lot of code to deal with, is to keep your function bodies in .sql text files and properly checked into a SCM. If you have to do a major name change, then you can use standard code refactoring techniques and re-apply the functions. Querying the pg_proc table (as damien noted) is a way to search after the fact, but having to do that suggests you're using the database to manage your code. merlin
В списке pgsql-novice по дате отправления: