Closed clach04 closed 1 year ago
@hab6 can you do me a favor and help me figure out the TODO item in the report? *TODO link to "no longer accept ODBC tacos"
Can you point me at the website/page that says we no longer accept ODBC? Thanks!
The Connector Tableau Exchange Submission Guide doc page has the following statement in section Step 1: Build and test your connector
Note: The Tableau Exchange no longer accepts submissions of ODBC connectors. Only JDBC connectors are accepted.
Thanks @hab6, description updated along with some timeline info.
I recommend we make ODBC and JDBC code identical as possible so that we can diff them to make it easier to see the wheat from the chafe before tackling https://github.com/ActianCorp/actian_tableau_connector/issues/25 (unless you already have positive changes/progress already). I have a hunch the number 2 items may explain some issues, the number of entries is suspiciously close to the number differences in failures, it could be a coincidence but easy to make the code match and then focus on diffs to remove any lingering doubt.
For white space diffs. see attached diff for:
diff -w -r actian_odbc actian_jdbc
looks "good" to me, so I think we can clobber the white space diffs.
@clach04 PR #28 - minor whitespace and formatting changes
Referencing comment, item #3 - Code diffs of interest
diff -r actian_odbc\manifest.xml actian_jdbc\manifest.xml
...
19,23c19,25
< <!-- See https://tableau.github.io/connector-plugin-sdk/docs/capabilities.html for capabilities names and explanations -->
< <customization name="CAP_ODBC_BIND_DETECT_ALIAS_CASE_FOLDING" value="yes"/>
< <customization name="CAP_ODBC_METADATA_FORCE_NUM_PREC_RADIX_10" value="yes"/>
< <customization name="CAP_ODBC_METADATA_FORCE_LENGTH_AS_PRECISION" value="yes"/>
< <customization name="CAP_ODBC_SUPPRESS_INFO_SCHEMA_TABLES" value="yes"/>
---
> <!--
> look at odbc connector and review CAP_ODBC_* for corresponding jdbc entries
> these are now documented as of mid Aug 2019 at
> https://tableau.github.io/connector-plugin-sdk/docs/capabilities.html#jdbc
> -->
> <customization name="CAP_JDBC_BIND_DETECT_ALIAS_CASE_FOLDING" value="yes"/>
Of the 4 ODBC capabilities listed in the diff, only one has a JDBC equivalent (see the Tableau Capabilities page for details). Summary of the listed diffs here:
ODBC Capability | JDBC Capability |
---|---|
CAP_ODBC_BIND_DETECT_ALIAS_CASE_FOLDING | CAP_JDBC_BIND_DETECT_ALIAS_CASE_FOLDING |
CAP_ODBC_METADATA_FORCE_NUM_PREC_RADIX_10 | No equivalent for JDBC |
CAP_ODBC_METADATA_FORCE_LENGTH_AS_PRECISION | No equivalent for JDBC |
CAP_ODBC_SUPPRESS_INFO_SCHEMA_TABLES | No equivalent for JDBC |
Therefore, I think no action is required to sync up the <customizations>
section between the ODBC and JDBC manifest.xml files.
Closing as complete/done.
From https://github.com/ActianCorp/actian_tableau_connector/pull/26 also related to https://github.com/ActianCorp/actian_tableau_connector/issues/24
ODBC xml file has less/different items in compared with the JDBC one
https://github.com/ActianCorp/actian_tableau_connector/blob/e7aae215602c84f28cbf8f14f33b0995e5bc1707/actian_odbc/manifest.xml#L56
https://github.com/ActianCorp/actian_tableau_connector/blob/e7aae215602c84f28cbf8f14f33b0995e5bc1707/actian_jdbc/manifest.xml#L58
diff -r actian_odbc actian_jdbc
returns more diffs than I was expecting:Majority of diffs are real js diff
Note shown, basically all the js code :-) - not interesting for this issue.
some (white space?) XML diffs
.. and more. See comment https://github.com/ActianCorp/actian_tableau_connector/issues/27#issuecomment-1681286854
Changes / TODO notes that need follow up
NOTE on JDBC requirement since 2022
Code diffs of interest:
Changes that need explaining/resolving