cfml

<@U01EY27APNH> on <https://helpx.adobe.com/uk/coldfusion/enterprise/faq.html> there's a link "systems support matrix" under "Which databases are supported?". It goes to <https://helpx.adobe.com/uk/pdf/coldfusion2023-support-matrix.pdf>, which 404s. Which is nicely played.

Looks like it should go to <https://helpx.adobe.com/pdf/coldfusion2023-suport-matrix.pdf>.

Nice speling of "suport" there.

Realy what I'm wondering about is why you don't suport *any DB with a JDBC conector*? What does it mater what DB is on the other side of the conector? That's... like... the whole idea of JDBC init?

Different versions of some JDBC drivers require different JDK versions and support different database versions -- so Adobe's "support" couldn't really cover all the bases there, so they only list what they've specifically QA'd/certified.

In addition, there are some tags in CFML that expand to SQL operations behind the scenes so it's possible those only work with certain JDBC drivers.

JDBC is a fairly permissive spec, unfortunately.

I support the Clojure community's two primary JDBC wrappers and I can tell you that features and behavior vary a *lot* across different drivers, and even different versions of the same driver sometimes. It's a _mess_!

&gt;  expand to SQL operations
Like specifical SQL statements that... would then necessary need to be in a specific SQL dialect?

No, I mean whose behavior might differ enough across drivers or versions to break the CFML tag.

Oh christ, yeah like `&lt;cfinsert&gt;` and stuff like that. Forgot anything existed except for `queryExecute` and `cfstoredproc`

(I don't know if the insert-related tag needs to get the newly-inserted key -- but the name of that differs across almost every JDBC driver)

They used to yet ya use a DSN type of "Other" and sling the settings for any (I presumed) old JDBC driver in there, provided you dropped the jar file into the lib dir. Was that kinda "use at yer own risk" sorta thing? I can recall needing to do that for some Oracle setups because the Oracle drivers CF shipped with were... not as good as they could be. This woulda been 20yrs ago though I guess.

My memory of that is that it was "caveat programmer"...

```Connecting to other data sources
Use the settings in the following table to connect ColdFusion to data sources through JDBC drivers that do not appear in the drop-down list of drivers:

Setting

Description

CF Data Source Name

The data source name (DSN) that ColdFusion uses to connect to the data source.

JDBC URL

The JDBC connection URL for this data source.

Driver Class

The fully qualified class name of the driver. For example, com.inet.tds.TdsDriver. The JAR file that contains this class must be in a directory defined in the ColdFusion classpath.```

So you can still use any JDBC driver you want but I wouldn't expect _support_ on it :slightly_smiling_face:

BTW, I think Mark is out through the new year due to the Adobe shutdown.