Ah, I see you'r referring to an earlier post above:
SQL Error 1312: PROCEDURE cant return a result set in the given context
How do you call your procedure?
A feature, of course. Oh man that joke is so outdated, that was not funny...
"I am not able to run" means what?
I am not able to run any stored procedure with nightly builds, is it a feature, or a bug? thnx
The recently refactored "Table tools" dialog has a new tab now: "Bulk table editor". What is bulk editing?
* Move all tables of one or more databases to another database
* Change default collation of these tables
* Change table engine
* Convert data to a different charset
* Reset auto_increment value
See it in action:
Great - thanks for looking at this Anse
See r2840 - no BOM's any more in written files, and mysqldump.exe reads these files without complaint. Hopefully that doesn't break other tools, but as I understand right it's more common that applications do not add BOM - so does Heidi now.
Funnily enough, the Wikipedia link I added to the previous post, although the URL to the page itself, only leads to a Wipedia search page. So click on "Search for UTF-8" on that page and select the first article listed to get to the intended page.
Further to djn's point, I did come across a Wikipedia article (I know it's not necessarily the most authoritative source) which lists a number of interoperability problems which arise as a consequence of BOM usage, amongst which was just the problem I was experiencing. See http://en.wikipedia.org/wiki/UTF-8.
Oh good point, some time ago since I read that. I'll try if removing that BOM breaks HeidiSQL's own detection of Unicode files while reading into the query editor.
Anse, are you sure the BOM is actually needed there? The Unicode consortium says that in UTF-8 usage of a BOM is permitted, but not reccomended - exactly because of such mismatches.