Re: Rule recompilation
От | Alex Pilosov |
---|---|
Тема | Re: Rule recompilation |
Дата | |
Msg-id | Pine.BSO.4.10.10107121604390.4070-100000@spider.pilosoft.com обсуждение исходный текст |
Ответ на | Rule recompilation (Jan Wieck <JanWieck@Yahoo.com>) |
Список | pgsql-hackers |
On Thu, 12 Jul 2001, Peter Eisentraut wrote: > Jan Wieck writes: > > > For most objects, there is no such "recompile" possible - at > > least not without storing alot more information than now. > > Create a function and based on that an operator. Then you > > drop the function and create another one. Hmmm, pg_operator > > doesn't have the function name and argument types, it only > > knows the old functions oid. How do you find the new function > > from here? > > In these cases it'd be a lot simpler (and SQL-comforming) to implement the > DROP THING ... { RESTRICT | CASCADE } options. This would probably catch > most honest user errors more cleanly than trying to automatically > recompile things that perhaps aren't even meant to fit together any > longer. Yes, I absolutely agree, and that's the aim of what I'm suggesting... -alex
В списке pgsql-hackers по дате отправления: