I should probably have brought up the last comment in separate email. As it
does not have to be viewed completely within a template framework. The
action would be a normal action, its just that the page module would need to
be modified so that action parameters would get parsed for .sql extension
and then the SQLAction would be invoked.
This action could store results in RunData in a standard way (or in the
session to support large queries), so that Screen modules could access the
data. With regard to templates, I would just like the support in the
service or page module to add these results to the Context, so that even
some dynamic content can be available to templates without writing Java
code.
>
> >
> > And one more thing I would like to see added is an SQLAction module that
> > takes a text file (we could standardize, so that an parameter like
> > action=selectusers.sql would automatically use the SQLAction) as input.
The
> > sql statement(s) could be parsed and submitted via Village or using
straight
> > JDBC. The results of the action should be automatically placed within
the
> > Context object for use within the template. (It may be that this is
moving
> > something that belongs in a Screen, so let's discuss proper placement.)
> > What I am essentially after is a way for people who are unfamilar with
Java
> > to use Turbine (of course someone in the organization is going to need
to be
> > fluent in Java,) to present db data. One might say this is going to
> > encourage application development in a non-OO manner, but some simple
> > applications and more to the point information management systems can be
> > built using something like the above and not suffer from the design.
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
