Bug #76107 | Cannot exclud longbloob field | ||
---|---|---|---|
Submitted: | 2 Mar 2015 19:26 | Modified: | 5 Mar 2015 14:59 |
Reporter: | Geverton Geverton | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.6.20 | OS: | Linux |
Assigned to: | CPU Architecture: | Any | |
Tags: | delete, field, longbloob |
[2 Mar 2015 19:26]
Geverton Geverton
[3 Mar 2015 14:56]
Peter Laursen
This ooks like a client issue to me (truncation, corruption or whatever in the client). I think you should tell what client you are using. I also wonder if the binary/blob value is used in the WHERE-clause of a DELETE statement (due to absence of a Primary Key, for instance). If you are using a GUI client, does it expose the full statement sent to the server? -- Peter -- not a MySQL/Oracle person.
[3 Mar 2015 17:30]
Geverton Geverton
Sorry. i solve the problem. it was a trigger.
[5 Mar 2015 14:14]
MySQL Verification Team
Thank you for the feedback. Are you able to provide the create table/trigger so the issue can be fully documented?. Thanks.
[5 Mar 2015 14:20]
Geverton Geverton
It was a simple trigger after delete. what happens is that the target table was as varchar instead of longblob.
[5 Mar 2015 14:59]
MySQL Verification Team
Thank you for the feedback.