Column Names should be encapsulated

[MarcusCulverTHL]

I recently pulled a data set where I named the columns "phone-uk"

Because for SQL Server these weren't encapsulated in square parentheses the import of the data set failed due to hyphens being a reserved character.

Column names (if abiding by best practise) should be qualified by square parentheses ( [phone-jp] ) to ensure the engine doesn't consider the hyphen as something else

[benkeen]

Thanks! Will add this in the next release.

[benkeen]

Sorry, I've been pulled into other things the last couple of months. Finally returning to this now, so expect an update in the next few weeks.

[benkeen]

I took a look at this and found a couple of related issues (the error message shouldn't have appeared when you used a hyphen and it had the wrong message), but encapsulating the column names seems to be working properly - see screenshot.

I haven't released the new version yet (should be hopefully later today). But if you still see a problem, just chime in here and I can re-open.