https://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-01-11T19:38:52ZEcoinformatics RedmineEML - Bug #2575: Data Manager Library: Support for query object APIhttps://projects.ecoinformatics.org/ecoinfo/issues/2575?journal_id=87882010-01-11T19:38:52Zben leinfelderleinfelder@nceas.ucsb.edu
<ul></ul><p>There are Java and XML query specifications at this point.<br />The Java API abstracts the SQL-specifics quite well (save for some reserved DB words as mentioned in bug <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: Exception when attributeName contains SQL keywords (Resolved)" href="https://projects.ecoinformatics.org/ecoinfo/issues/2737">#2737</a>).<br />The XML goes one step further and allows you to pass an XML representation of the query to the DML where it is parsed and turned into the Java version of the query.<br />Both mechanisms return a ResultSet to the calling application. There are ways to get at the resultset columns using attribute name/label/index translations and this can be useful when dealing with synthetic datasets (where many tables have been joined). I agree that the "safest" way to access the columns may be by index because of the fact that EML allows us to reuse attribute names.</p>
<p>Unless I've misread this bug, I believe it is resolved. Please reopen if not.</p> EML - Bug #2575: Data Manager Library: Support for query object APIhttps://projects.ecoinformatics.org/ecoinfo/issues/2575?journal_id=87892013-03-27T21:20:38ZRedmine Admin
<ul></ul><p>Original Bugzilla ID was 2575</p>