CSV Import

[Sandy]

Just tried a CSV import and the new option for the Separator type to `Auto Define` does nothing. Not sure what it was supposed to do but I would expect that it would determine the Separator from the file contents????. If that's the case doesn't work.

Using 7.3.131

Sandy

[alexa]

The option works correctly. It defines the separators Tab, Space, Comma, Semicolons.

We suspect that there are separators in your file that differ from Tab, Space, Comma or Semicolons.

If you, first, performed export and then import (through dbForge), selecting/unselecting the option will make no difference.

If you want your specific separator to detect, you have to unselect the option Auto Definer and
specify the necessary symbol in the Custom field (which is beside). Mixed separators won't be detected.

[Sandy]

Odd it's a straight up CSV export from googledocs. It has a header and is only comma separated so not sure why it doesn't auto detect if I select the comma ', ' as the sep it works just fine on import so should have no reason to not detect the correct one.

I'll take a look in the file and see if anything looks odd.

[alexa]

Could you please send us for investigation the google doc and csv file that you have exported?

You can send a reply straight to our support system at alexaATdevartDOTcom and supportATdevartDOTcom .

[Sandy]

Alexa -

Just sent it to you and support emails.

Thanks
Sandy

[alexa]

Thank you for the reply.

This is not supported in dbForge. Though, we will review supporting it in one of the next product versions.

[Sandy]

Alexa -

Not Supported? It's the most basic form of a CSV file. It imports just fine if you select CSV Separator as a ',' (comma) just doesn't auto recognize it.

Otherwise works great for importing so can't see why it wouldn't be able to pick up the Separator.

In any case not a big deal, more FYI that it can be better for a common source of exports like Google Sheets CSV.

Sandy

[alexa]

Thank you for the information.

We will take this into account.