>>>>> "jw" == jwalt-axkit <iso-8859-1> writes:
jw> Am Thursday, 28. August 2003 14:28, schrieb Tom Schindl:
>> Well I need some informations from a database(small part) and
>> some from XML-Files. If all data comes from a database I'd
>> agree with you. Still when having data from different sources
>> like I have I think I've the following possibilities:
>>
>> 1) Using axkit:-URIs => XSP->DBI->XML
>> 2) Using xincludes
>> 3) Embedd my SQL-Queries into XSL with a construct something
>> like this:
>>
>> --------------------------8<--------------------------
>> <xsl:value-of select="document( 'dbisql:/SELECT_*_FROM_foo'
>> )/test"/>
jw> Using SQL queries inside URL's is generally considered bad
jw> practice - you can easily get bitten by SQL injection and
jw> whatnot. I have a prototype SQL provider (and a more advanced
jw> design which I will release when done) which lets you access
jw> either selected rows of any table you want, or lets you define
jw> fixed queries which you can later retrieve via
jw> document('sql:myquery/2.xml') (selecting row nr. 2 of your
jw> query). I can send it to you if you want to play with that,
jw> but you also need to patch AxKit in order to have the 'sql'
jw> pseudoprotocol recognized. The provider is quite limited, but
jw> it seems to fit your requirements very well. Tell me if you
jw> want it. A more generic version of it will be released later.
This sounds fun!
One of the problems I've had with all of the SQL taglibs is that I
usually want at least some of the functionality in non-AxKit
applications.
I usually end up encapsulating the DB with a Perl module. For AxKit I
wrap that in a thin taglib or provider; other applications just
interact with the module directly. Is this what everyone else does, or
is there a better way ?
Cheers,
--
M.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
