I think you are right about pushing it to the application level.
This is the kind of thing that can have too many use cases.
Maybe the best I can do is to provide a JDBC sample.
Paulo
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Geir
> Magnusson Jr.
>
> Paulo Gaspar wrote:
> >
> > > Jason too care of that a while ago. A JDBC loader? :)
> > >
> > > geir
> >
> > Yeahp. I work a lot with JDBC and it would be easy for me.
> > Feature sugestions?
>
> First, yeah, I think this would be useful for people. (Of course,
> what's wrong with your filesystem ?)
>
> However (there had to be a however, right... :) I live in the "what can
> be pushed to application layer should be pushed into application layer"
> camp a lot of the time, and wonder if this would be a great tool for
> applications.
>
> Something that would return a Template so you could use it in servlets
> or in apps. That would then punt what could be ugly permissions /
> config / setup / connection pooling / etc issues to the application
> layer, where that stuff is usually handled already anyway.
>
> Thoughts?
>
> geir
>
>
> --
> Geir Magnusson Jr. [EMAIL PROTECTED]
> Velocity : it's not just a good idea. It should be the law.
> http://jakarta.apache.org/velocity
>
