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

ODBC Support #6435

Open
simonaubertbd opened this issue Apr 26, 2023 · 3 comments
Open

ODBC Support #6435

simonaubertbd opened this issue Apr 26, 2023 · 3 comments
Assignees

Comments

@simonaubertbd
Copy link

What's your use case?
I would like to connect through oledb to an existing database (MonetDB here)

Well, I can't connect to the said database :)

What's your proposed solution?
The SQL Table Widget should allow a connection through ODBC

Are there any alternative solutions?
Using excel to export data in file... but it's an alternative like coca cola is an alternative to coffee.

@janezd janezd added the needs discussion Core developers need to discuss the issue label May 4, 2023
@PrimozGodec
Copy link
Contributor

Hi, I have already started to work on that through the SQL-alchemy module #5079 in the past, but then newer finished due to lack of time. When I have more time, I will continue on that, but I think we need to clean up the model first since the last time, I run into some implementing issues due to some current functionalities.

The task would be:

  1. cleanup and simply the SQL backend and Table module (removing untested and unmaintained delayed loading functionalities)
  2. Implementing loading through SQLAlchem, ODBC (maybe Pandas)

@PrimozGodec PrimozGodec removed the needs discussion Core developers need to discuss the issue label May 12, 2023
@simonaubertbd
Copy link
Author

@PrimozGodec Hello and thanks for the answer. As I said before, I have a huge Alteryx background and in Alteryx there are two modes :
-in memory ; you can read data from database (like a select * with odbc, oledb or api) and then prepare it on your machine with local computation and then output it where you want, including a database
-in database : your workflow generates sql query and the data stays in database where it's processed.

The second mode is hard to develop for Orange because it's all python based, I understand. However, the first one doesn't seem that hard because it only requires change in one widget.

@simonaubertbd
Copy link
Author

Hello @PrimozGodec I tested #pyodbc and it works pretty fine. It's implemented this week on the Amphi project.
For reference :
https://pypi.org/project/pyodbc/
amphi-ai/amphi-etl#14 (comment)

Best regards,

Simon

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

3 participants