Skip to content
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

New dbplyr interface #92

Open
stibu81 opened this issue Sep 27, 2022 · 8 comments
Open

New dbplyr interface #92

stibu81 opened this issue Sep 27, 2022 · 8 comments
Assignees

Comments

@stibu81
Copy link

stibu81 commented Sep 27, 2022

When I use RClickhouse 0.6.4 from CRAN I get the following warning:

<ClickhouseConnection> uses an old dbplyr interface
ℹ Please install a newer version of the package or contact the maintainer

This is due to a change in the interface that started with dbplyr 2.0.0 (see here). For now, this is just a warning and RClickhouse still works as expected, but according to the aforementioned page, the old interface will stop working around mid-2023 (12 months after the publication of version 2.2.0 in June 2022).

Do you intend to fix this in time? This would be highly appreciated.

@inkrement
Copy link
Member

Hi Stefan, thanks for reporting! We'll take a look at it.

@stibu81
Copy link
Author

stibu81 commented Sep 27, 2022

Excellent, thanks! If I can assist, let me know.

@stibu81
Copy link
Author

stibu81 commented Nov 24, 2022

Any news on this?

@inkrement
Copy link
Member

@dariayudaeva already works on this task. Since there is still some time left until mid-2023, it is not our top-1 priority. Anyhow, you can track the latest changes in her fork: https://github.com/dariayudaeva/RClickhouse

@dariayudaeva
Copy link
Collaborator

Hi, thanks for reaching out! Overall, it should be mostly fixed by now, but we wanted to test everything again to make sure. :) Will finish soon.

@stibu81
Copy link
Author

stibu81 commented Nov 24, 2022

Thanks for the good news! As you say, there is no need for a rush, but it's good to know that you're taking care of this. Thank you for your efforts!

@tel
Copy link

tel commented Nov 2, 2023

Hi team, it's been a bit under a year since the last comment. I'm using package version 0.6.8 and still receiving this error. I'm curious if there's been motion here.

@inkrement
Copy link
Member

The problem should already be fixed. If it is still incorrectly displayed in the current version, there is probably still a bug or the deployment failed. We will look into this. However, I can't say how long this will take due to the current lack of time. We would be grateful for external support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants