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.

Sign up for GitHub

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

Jump to bottom

Allow for custom field separator when importing CSV files #23

Closed
justinclift opened this issue May 26, 2014 · 4 comments
Closed

Allow for custom field separator when importing CSV files #23

justinclift opened this issue May 26, 2014 · 4 comments
Labels
enhancement Feature requests.
Milestone
3.2 - Codename Ra...

Comments

@justinclift
Copy link
Member

A request in one of the SourceForge comments:

I noted the inability to specify a custom field separator character when importing
a CSV file as a table. This may be a minor omission but it prevented me from
undertaking a crucial task.

If it's not hard to add, it sounds useful.
MKleusberg added a commit that referenced this issue May 30, 2014
@MKleusberg
ImportCsvDialog: Add options to define custom quote/separator chars
55435e2 
Make it possible to use other quote and separator characters than those
predefined in the respective combo boxes when importing a CSV file.

See issue #23.
MKleusberg added a commit that referenced this issue May 30, 2014
@MKleusberg
ExportCsvDialog: Add option to define custom quote/separator chars
f8b2dd0 
Make it possible to use other quote and separator characters than those
predefined in the respective combo boxes when exporting a CSV file.

See issue #23.
@MKleusberg
Copy link
Member

I've added the required input fields to the CSV export and import dialogs in the above mentioned commits. For even more exotic export formats I'd suggest using the search & replace option of a decent text editor or writing an awk/sed/perl/python/... script.

@justinclift
Copy link
Member Author

Cool. :)

One thing that some other SQLite programs seem to have, is a M$ Excel (.xls) export. No idea how relevant/useful that would be. People can open an issue for it if they want it. 😉

@justinclift justinclift added this to the 3.2 - Codename Radiant milestone May 30, 2014
@MKleusberg
Copy link
Member

Oh that would require quite a bit of code 😮 I'd suggest exporting it to CSV in this case and then open that in Excel. Should lead to the same result in most cases.

@justinclift
Copy link
Member Author

Yeah, that'd be my approach as well. 😄

@SilvioGrosso SilvioGrosso mentioned this issue Dec 20, 2018
Open
@cmvizitiu cmvizitiu mentioned this issue Dec 24, 2018
Closed
10 tasks
@scottfurry scottfurry mentioned this issue Jan 30, 2023
Open
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Feature requests.
Projects
None yet
Milestone
3.2 - Codename Radiant
Development

No branches or pull requests
2 participants
@justinclift @MKleusberg