CurtHagenlocher commented on issue #3220: URL: https://github.com/apache/arrow-adbc/issues/3220#issuecomment-3141128821
The design of this aspect of the API probably dates back to ODBC 1.0 and is clearly influenced by the `LIKE` feature of SQL (which I assume is often used to implement it). If I want to say "show me all the tables starting with `spt_` then I need both a way to match an arbitrary suffix and potentially a way to say that the underscore isn't a wild card. In some dialects of SQL, this might turn into `select * from INFORMATION_SCHEMA.TABLES where TABLE_NAME like 'spt[_]%'`. But while I think there's a use case for being able to do this, it's a nontrivial change and perhaps not of very high value. I think we could solve the more-immediate problems people have had with a more incremental change: define a standard connection property e.g. `"adbc.connection.get_objects.disable_wildcards"` where if set to `"true"` on a driver that supports it, the driver will treat the identifiers as literal. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
