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

Pyclient: add filename/path to export method and add possibility to return exported data in memory #4133

Closed
YpeZ opened this issue Aug 15, 2024 · 0 comments · Fixed by #4183
Assignees

Comments

@YpeZ
Copy link
Contributor

YpeZ commented Aug 15, 2024

Is your feature request related to a problem? Please describe.
When exporting data using the export method, the data is saved by the name of the table or schema in the working directory of the user. This is sometimes unwanted as user may be working on, for example the same table from different schemas where the export of one would overwrite the other on the disk. Often, a different directory than the working directory for saving the data is preferable. Additionally, users might only need the data to be in memory and not saved on the disk at all.

Describe the solution you'd like

  • Add the option to specify the path and filename for the export
  • Let the method return the exported data
  • Add the option to not save the data on the disk
@YpeZ YpeZ self-assigned this Aug 15, 2024
@YpeZ YpeZ changed the title Pyclient: add filename to export method and add possibility to return exported in memory Pyclient: add filename to export method and add possibility to return exported data in memory Aug 15, 2024
@YpeZ YpeZ changed the title Pyclient: add filename to export method and add possibility to return exported data in memory Pyclient: add filename/path to export method and add possibility to return exported data in memory Aug 15, 2024
@YpeZ YpeZ linked a pull request Sep 11, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant