Export (Clipboard)

We are living in the age of AI and since about a week ago, for some other reason, Claude now in the desktop version accepts the / as a skill command

Is there a way to prevent it when I do an export to the clipboard (or file) to get rid of all these prefixes before the information about the table comes up?

/!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT /; /!40101 SET NAMES utf8 /; /!50503 SET NAMES utf8mb4 /; /!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE /; /!40103 SET TIME_ZONE='+00:00' /; /!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 /; /!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' /; /!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 /;

If not the programmers should seriously consider having an option to remove all of that information.

You sound like a kid demanding that every scripting/coding language should drop the semicolon just because yo momma said it's bad for your teeth. Who cares what Claude wants? The next mooface will probably demand something real daft as ChatGPT wants something else. Et cetera, yada, yada ...

How about you ask the Claude peeps to drop that crap or give you a setting to switch off skill interpretation instead of coming here and whining? After all, comments, delimiters and such have been around long before Claude, so either they make up their own shebang or damn well get used to people complaining.

In your verbiage (emphasis mine) "If not the CLAUDE programmers should seriously consider having an option ..."

Those "prefixes" contain queries which ensure data integrity during the import of that file. I cannot remove them without seriously breaking it.

These conditional comment/queries are there since more than 20 years. Not only in HeidiSQL, mysqldump and other clients produce similar stuff. You do not want to remove them, if you want intact data.

That mix-up with skill commands is an embarrassing bug in Claude, not an issue in HeidiSQL. Claude should use a part of its own intelligence to detect they are SQL commands, not skill commands.

"ansgar" Thank you. Your explanation makes sense and I understand completely.

"TTSneko" It's because of assholes like you that Stack Overflow is busy seeing their arse. I didn't offend you in any way. I just asked the question: Why do you see the need to be sarcastic?