From: Adriano d. S. F. <adr...@gm...> - 2013-06-23 18:18:42
|
Hi! This error is inconsistent in 2.5 and 3.0! 2.5 accepts a DECLARE for a denied module, but rejects it if a procedure references the function. This happens because DFW does not load the just declared function, but it happens when it is referenced. This is at least strange. In 3.0 DFW loads it and rejects it right on the declaration. But it happens then that restore may not work (I guess it may not work in 2.5 too). Currently this error in restore makes metadata wrong and causes somewhat unrelated crashes with procedures not completely loaded. Adriano |