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
Invalid types in INSERT if not all columns are imported from CSV #327
Comments
This issue is about Heidi parsing the file (client parses file contents), which is your only option on MSSQL. With your settings (LOAD DATA INFILE, or server parses file contents), Heidi does not even convert any types, so no conversion can fail. |
I see. |
I have tested again with MySQL and "Client parses file content" option selected (everything else as in my previous reply). HeidiSQL issued the following query on import: So there is no issue with first auto increment column, however there is an issue with last row's value (notice quote with \r added). I've created a separate ticked for the issue. |
Because I'm running into this bug again, I'm gonna post a minimal example:
|
Are you sure that fixes the issue? |
Ok, so I guess I can close this. |
@ansgarbecker Please close #242, seems to be a duplicate. |
The CSV import feature is mostly useless. If the file is missing columns, they must be the last few columns (not in-between or at the start) or the table must be of only one type.
Steps to reproduce this issue
(Minimal example.)
Current behavior
Heidi tries to use the first column's type to insert the second column's values as it doesn't care what you checked or not when it determines the column types.
Expected behavior
Heidi must consider unchecked columns when determining what type to import a value as.
Environment
each and any
See also
#242
The text was updated successfully, but these errors were encountered: