-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[cmake] Deprecate mysql, odbc, pgsql build options
#17423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thanks for the heads up. It is enough to turn the options OFF, right? |
|
If nobody uses it, yes. The deprecation message will print if the option is set to |
|
I'm in favor of deprecating mysql, odbc, pgsql. But not sqlite. It is used, e.g., by cvmfs to use RDataFrame on sqlite data. |
Test Results 18 files 18 suites 4d 7h 48m 2s ⏱️ For more details on these failures, see this check. Results for commit 077b6d1. ♻️ This comment has been updated with latest results. |
All of them require (optional) dependencies for very little use.
mysql, odbc, pgsql, sqlite build optionsmysql, odbc, pgsql build options
|
Oh yes, my bad: I didn't realize |
|
AFAIK, the |
I think the main question for me is whether it is used. Do we know of anybody relying on it? Eventually I'd personally like to see all SQL-related classes deprecated and removed from ROOT because I don't think we should encourage their use. |
OK fair enough, let's deprecate it and we'll see |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
All of them require (optional) dependencies for very little use.
FYI @andresailer