From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | PegoraroF10 <marcos(at)f10(dot)com(dot)br>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: execute block like Firebird does |
Date: | 2018-02-12 17:08:13 |
Message-ID: | 45ecb017-06af-ed3c-dfdc-be32ce0df924@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/12/2018 08:57 AM, PegoraroF10 wrote:
> I know I need to think a different approach of what execute blocks does on
> Firebird.
> What I was trying to was just let them the way they were wrote, because
> their results are correct and with more time replace them to a new way.
That may not be necessary. As someone mentioned upstream you maybe able
to replace the EXECUTE BLOCK with CREATE OR REPLACE FUNCTION and then do
some clean up/additions to the enclosed code. To be more certain about
this we would need to see a complete example of one of EXECUTE BLOCKs.
If that is possible for security reasons, then a made example that does
the same thing.
>
> But, if that way cannot be used, I´ll probably write some hundred of
> functions right now and use them, because this way works for sure. And then,
> with more time to spend, I´ll replace them one by one.
Why? Once you create the functions and they do the task what is the
purpose of replicating them and more to the point how would you?
>
>
>
>
>
> --
> Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Atkins | 2018-02-12 17:18:29 | Re: persistent read cache |
Previous Message | PegoraroF10 | 2018-02-12 16:57:05 | Re: execute block like Firebird does |