RFC: LogReport Architecture
Joost van Baal
joostvb at logreport.org
Sun Jun 24 00:10:27 CEST 2001
On Sat, Jun 23, 2001 at 10:34:47PM +0200, Egon Willighagen wrote:
>
> I'll explain my need for an advanced mechanism:
>
> 1. before step 2. comes into play i need to do some basic
> SQL query to do a preselection
What 'step 2.' are you talking about? Did I miss something?
> 2. i'll need access to a program external to Lire
Are you talking about the same thing as to which I was refering, when
I wrote, in Message-ID: <20010622225624.C30096 at gelfand.mdcc.cx>
>> Simple reason: i need the flexibilty when making advanced
>> subreport this summer... I will need to do things which you cannot
>> do in SQL, or any scripting langauge.
>
> What plans do you have?
? Could you please tell what exactly your plans are? We might get
synergy.
>
> this is the program R (http://www.r-project.org/)
> which i will need to do the statistical analysis,
> like prediction of load/usage etc and for clustering
> of data...
>
> R can be scripted, so a system call will do
>
> 3. and the results of R need to be reformatted into
> the OUTPUT interface format
>
> This can probably not be done with some basic scripting
> langauge.
You are talking about the need for a complete turing-machine-like language
to build queries for the dlf files? I believe the suggestion which has
been made to introduce a simplified language, but next to that still
keep it possible to interface with fullblown perl or shell, is valuable.
If the drawbacks of such a possibility are not too bad, we surely should
enable this.
Bye,
Joost
--
To UNSUBSCRIBE, email to development-request at logreport.org with a subject of
"unsubscribe". Trouble? Send an email with subject "help" to
development-request at logreport.org
More information about the Development
mailing list