Yusuf


>understood?

Getting there. What are the 20 lines of script?

Roy

Roy Lambert wrote:

> Getting there. What are the 20 lines of script?

Can be anything, i.e. calculating a m3 from length/width/height or
something total different. This is based on customers need. Anything.
I think we can't do this with actual Edb-Server. We need something like
"ExecScript" from tedbquery component, ie. EXECUTE SCRIPT IMMEDIATE to
make it work.

It is not important right now, but would be a good new function for Tim


--
--
Yusuf Zorlu | MicrotronX

On 9/26/2019 11:07 AM, Yusuf Zorlu wrote:
> Can be anything, i.e. calculating a m3 from length/width/height or
> something total different. This is based on customers need. Anything.
> I think we can't do this with actual Edb-Server. We need something like
> "ExecScript" from tedbquery component, ie. EXECUTE SCRIPT IMMEDIATE to
> make it work.
>
> It is not important right now, but would be a good new function for Tim

External function (in external module) should work for this

Raul

Yusuf


My problem is you've given a couple of simplistic examples and seem to be wanting to throw any old requirement and expect it to work. Tim may know a way of doing this I certainly don't.

Raul has a valid approach but only if you write specific code for each requirement and given that you don't want to write procedures I can't see that helping much.

What is required may be to build your own interpreter. Something I did to implement mail & news rule processing.

Roy Lambert

On 9/27/2019 2:53 AM, Roy Lambert wrote:
> Raul has a valid approach but only if you write specific code for each requirement and given that you don't want to write procedures I can't see that helping much.

Roy,

I think you can write a generic external module that is basically
tedbquery and simply executes script to send in - i'm not proposing to
write multiple external functions but just one generic "runscript" one.

Raul

Raul


Ah, you're proposing he writes his own EXECUTE IMMEDIATE, interesting, but unless I'm missing something he'd also need to build a script parser into the external function.

Roy Lambert

Yusuf,

You could have the SQL code of the custom tasks in CLOBs and add a functionality to your application to automatically generate a stored procedure for each task when appropriate. Then, an existing JOB would read the list of stored procedures to execute, that could be in a table too.
Easy and clean. There is no need reinvent the wheel.
 
--
Fernando Dias
[Team Elevate]

Fernando


Or even less wheel inventing - just write the procedures <VBG>

Roy Lambert

Roy,

Right

--
Fernando Dias
[Team Elevate]

Thanks guys, we'll write the procedures when needed and delete them
when there is no need for them.

--
--
Yusuf Zorlu | MicrotronX