-
Notifications
You must be signed in to change notification settings - Fork 60
Problems importing .csv file into database #116
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
Comments
Hi @5av10ur , thx for reporting the issue! |
@OllisGit I am getting the exact same issue that @5av10ur has, that replacing the database fails with the popup showing the "Parsing/Importing line:" with the total number of lines. |
Attached is the .csv file. Let me know if I did anything wrong with this or whether it helps.
From: OllisGit <[email protected]>
Sent: 02 February 2021 20:24
To: OllisGit/OctoPrint-SpoolManager <[email protected]>
Cc: Leo Walton <[email protected]>; Mention <[email protected]>
Subject: Re: [OllisGit/OctoPrint-SpoolManager] Problems importing .csv file into database (#116)
Hi @5av10ur<https://github.com/5av10ur> ,
thx for reporting the issue!
Could you please attach the csv file to the issue, so that I can reproduce the error?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#116 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIP45ZM3LJNMNPEEZ3J4CH3S5BNOPANCNFSM4WVERKOQ>.
|
Hi @5av10ur! fyi: Answering via email and attaching a file doesn't work in GitHub. |
Hi, Please test and give me a feedback. Thx, in advance |
I'm trying to import a database of spools I have created and have had some issues with the importing process.
I downloaded the sample .csv file and added my records to it ready to import. I selected to replace the existing database rather than append as I was starting from new. When I first started to import it threw an error: "Error parsing value '02.06.2019' for field 'Purchased on [dd.mm.yyyy]': invalid literal for float() 02 06 2019" despite the field being formatted as dd.mm.yyyy as per the other date fields.
After a bit of investigation it turns out that, despite the field header stating that the format for this column is [dd.mm.yyyy] it actually should be [dd.mm.yyyy hh:mm] so I added 00:00 to each field entry which cleared the parsing error. Now, however, it just hangs when parsing the final line. The pop-up window shows "Status: running" and "Parsing/Importing line: 11" (which is the total number of lines in the .csv file including header) but never moves on from this.
To solve this I had to select "Append to Database" rather than Replace. I have no idea why Replace didn't work but I did get the plugin to import the database eventually. I post this in case others have a similar problem and this helps them.
The text was updated successfully, but these errors were encountered: