I should say what I mean and mean what I say. :-) In an effort for
brevity, my example included the simplest functions I could think of off
the top of my head. In reality, they are large PL/PgSQL beasties. Good
to know that it won't work for plain ole SQL functions, though...we've
got some of those too. Thus, I'll have to enforce the loading order
after all. Thanks for the info Tom.
-Fran
>>drop function bar();
>>drop function foo();
>>create function foo() returns int4 as '
>> select bar();
>>' language 'sql';
>>create function bar() returns int4 as '
>> select 1234;
>>' language 'sql';
>
>
>>This loads into the db just fine.
>
>
> It does?
