/* SQL Error: Unknown column 'name' in 'field list' */
VALUES (.192,4,1,-1,"Pwned","Pwned","Pwned","Pwned",38699,6,0,100,100,1,-1,-1,1,70,0,0,0,0,0,0,0,1,1,0, 1,99999, 3,99999, 4,99999, 5,99999, 14,99999, 21,99999, 20,99999, 19,99999, 7,99999, 13,99999,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,90000000,99999999,99999999,99999999,99999999,99999999,99999999,0,0,0,35844,1,0,0,0,0,18060,1,0,0,0,0,17713,1,0,0,0,0,35842,1,0,0,0,0,35894,1,0,0,0,0,1,"Pwnage Server GM GEAR",0,0,0,0,0,-1,0,0,0,90000000,0,0,0,0,0,0,2,0,1,0,4,0,104,0,0,0);items
It's been 4 years. The joke is dead beyond resurrection.
SQL Error: Unknown column 'name'
The weapon script is incompatible with the WoW server software package you're using.
The server software package contains the table definition, which in this case does not match with the weapon script in terms of defined columns.
Perhaps the script is designed for another package, or perhaps just for another version.
a. Use some other server software, specifically use the one that your weapon script was designed to work with.
b. Use another weapon script, or weapon script generator (whatever), specifically one designed to work with the server you're using.
The "Unknown column 'name'" is a server-side message and means exactly that it says—not sure why everybody's assuming there's a long standing bug in HeidiSQL that prevents MySQL Server from recognising columns.
To see column names, find the table in the left pane, click on it and inspect the "Table" tab. You should see the list of columns in the bottom half. Additionally, the "CREATE code" contains some SQL you can share in your favourite SQL forum to help others reproduces issues.
Your database uses some troublesome naming convention are you aren't escaping column names as needed. You claimed your code looks like this:
UPDATE streamer SET data1 = '0';
... but the screenshot shows something like:
UPDATE streamer SET zipfm64a.aac = '0';
... and you do not have any
zipfm64a table or a
aac column. You probably want:
UPDATE streamer SET `zipfm64a.aac` = '0';
You would face the same issue in any other MySQL client.
Please login to leave a reply, or register at first.