Studio debug error "Data too long for Column in_watch_value

Discussion of open issues, suggestions and bugs regarding database management and administration tools for MySQL
Post Reply
abelekj
Posts: 3
Joined: Tue 11 Nov 2008 15:49

Studio debug error "Data too long for Column in_watch_value

Post by abelekj » Wed 06 Apr 2011 14:43

How can I execute Debug when I have a long string. I have defined a VARCHAR(4000) variable in my code to match the definition in the database. When I execute a FETCH (in debug mode) I get the error "Data too long for column 'in_watch_value' at row 72. This occurs at the command where I execute a FETCH against the table that contains the long string. Should I be using a different variable type of is my dBForge configuration incorrect. The code seems to work when not in DEBUG mode but I need to look at the logic more closely. I DO NOT have any watchpoints set so I do not know how to proceed. I have tried typing the variable as VARCHAR, MEDIUMTEXT, LONGTEXT and BLOB with the same error. Any help would be appreciated

Alexz
Devart Team
Posts: 165
Joined: Wed 10 Aug 2005 08:30

Post by Alexz » Thu 07 Apr 2011 07:02

Could you specify the full version of dbForge Studio for MySQL? You can learn it from the About dialog (the Help->About menu).

abelekj
Posts: 3
Joined: Tue 11 Nov 2008 15:49

Post by abelekj » Thu 07 Apr 2011 15:11

I am running Standard Edition dbForge Studio for MySQL version 4.50.300

.jp
Devart Team
Posts: 345
Joined: Wed 09 Sep 2009 06:55
Location: devart

Post by .jp » Fri 08 Apr 2011 07:19

abelekj wrote:I am running Standard Edition dbForge Studio for MySQL version 4.50.300
This build is very old. Please download the latest build (4.50.348) and check whether the problem persists.

abelekj
Posts: 3
Joined: Tue 11 Nov 2008 15:49

Post by abelekj » Fri 08 Apr 2011 14:42

Upgrading did resolve the problem. Thanks.

Post Reply