Bug #7795 Datatyp integer causes Access violation
Submitted: 11 Jan 2005 9:08 Modified: 11 Jan 2005 15:51
Reporter: Thorsten Schuecking Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:5.0.2 OS:Linux (SUSE 9.2 & Windows XP Prof.)
Assigned to: Michael G. Zinner CPU Architecture:Any

[11 Jan 2005 9:08] Thorsten Schuecking
Description:
environment: 
Server: 
(NOVELL) SUSE LINUX 9.2 professional i386 (Intel Celeron 1.4)
or
(NOVELL) SUSE LINUX Enterprise Server 9 i386 (Intel P4 2.66)

Database:
MySQL-server-5.0.2-0.i386.rpm
MySQL-shared-5.0.2-0.i386.rpm
MySQL-client-5.0.2-0.i386.rpm
MySQL-devel-5.0.2-0.i386.rpm

Client: 
mysql-query-browser-1.1.5-win.msi or mysql-administrator-1.0.18-win.msi

"Edit Table" (dropdown menu MySQL Query Browser) could not open table attributes
if a interger type is selected for any row. 
The statusbar shows:
Access violation at address 0034C1B0 in module 'libmysqlx.dll'. Read of address 00000000.
The error is reproduceable as follows:

1st Step:
CREATE TABLE 
test_2 (ID varchar(10),col1 varchar(10),col2 varchar(10), PRIMARY KEY(ID));

The new table is accessable via edit table drop down.

2nd:
ALTER TABLE test_2 CHANGE col2 col2 INT(4);

The altered table now is no more accessable via Edit Table drop down.

Changing column type to varchar makes the table editable again,
from MySQL query browser.

We only could fix the problem instllalling MySQL Server 5.0.1

Many thanks! & Best Regards,
Thorsten Peleikis

How to repeat:
MySQL 5.0.2 RPM i386 Version 
on 
NOVELL SUSE LINUX enterprise Server 9 
or 
SUSE LINUX 9.2 professional

"Edit Table" from MySQL Query Browser (WindowsXP) and MySQL Administrator does not work if a data type intger is select for one or more column is selected.

The statusbar shows:
Access violation at address 0034C1B0 in module 'libmysqlx.dll'. Read of address 00000000.

Installing  MySQL Server 5.0.1 fixes the problem.
[11 Jan 2005 15:51] Michael G. Zinner
Thanks for reporting. The problem is not located in Query Browser but in the MySQL Sever. It has already been fixed and will be in the 5.0.3 release.