Hi Ian,
I don't know, but the code change I'm seeing in JDBCDataStore is not where
I expected it... maybe it bears some relation.
The check on whether a visitor can be optimized out or not is normally made
at the beginning of this method:
While experimenting with function handling in JDBC datastores I added a new
test as a just in case test - it should already pass on all databases. I
was just checking strMatches functions didn't get passed to the database
and all seemed fine with H2 and Postgis locally, when I pushed it to gtihub
