Hello,
We (I personally) wrote most of a AR-JDBC plugin once upon a time. But I
quickly concluded that the job had a high maintenance factor (as the specs
change). We therefore took a different view and implemented an AR to SQL
translator into XML Gateway query requests. Look at this:
<query type="sql">
<template>sampleARSQL</template>
<searches><search>
<server>myarsqlserver</server>
<select>"Group List", "Full Name"</select>
<from>"User"</from>
<where>"Login Name" = 'xmlgwtest'</where>
</search></searches>
</query>
You'll note that I am referring to the User form and field names. Of course,
these do not exist in the database as it uses T tables and C columns. The XML
Gateway translates these declarations into SQL using T tables, C columns
(etc.) and executes the SQL directly against the ARS database using JDBC.
Therefore, all a user needs to do is put the correct JDBC driver into the
gateway, tell it how to connect directly (using the JDBC driver) and execute
the above XML query.
The result is rapid access to ARS data because going via the XML Gateway &
JDBC is hundreds of times faster than via ARS server/ARAPI.
John
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
