This one time, at band camp, Matthew Lehrian said:
ML>I'm trying to use Castor with OpenBase. I can successfully connect and
ML>read basic tables into data objects; however, I'm having problems with
ML>the outer join syntax that Castor is generating. Since I'm using a
ML>generic JDBC driver, it seems that Castor is producing SQL-92 JDBC
ML>code. Is there a way I can control how the SQL code is generated?
ML>
ML>For example, Castor generates the following:
ML>
ML>SELECT Customer._rowid,Customer.customerName,Product._rowid FROM {oj
ML>Customer LEFT OUTER JOIN Product ON Customer._rowid=Product.customerID}
ML>
ML>However, this is what I need:
ML>
ML>SELECT Customer._rowid,Customer.customerName,Product._rowid FROM
ML>Customer,Product WHERE Customer._rowid*Product.customerID
Matthew,
The only way that this can be controlled is by implementing a driver
for OpenBase. The drivers are located in
src/main/org/exolab/castor/jdo/drivers. By implementing the driver
yourself, you'll have direct control over the SQL generated for
OpenBase.
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
