Problem with MySQL management project [SOLVED]

[parodid]

Test-MySQL.zip

Example project

(11.24 KiB) Downloaded 339 times

Dear Mr. Pagès,

I suspect there is a bug in MySQL 'not null' field's flag management because Boml continuosly 'forgets' its value if the field it's described as a primary key.
After saving it as checked I found it unchecked the next time I re-open the project.

Please, see the 'table' db table in the attached example project.

Best regards.

[Bruno Pagès]

Dear Mr. Parodi

I don't understand you, when you edit a primary key the toggle "not null" doesn't exist, so you cannot set it and it cannot be 'forget' when you reload the project

By definition a primary key is not null

Best regards,

Bruno Pagès

[parodid]

I mean the flag in the 'Associated column' of the primary key.
The produced SQL is:

Code: Select all

DROP TABLE IF EXISTS `tables`;
CREATE TABLE `tables` (
  `id` INT(11) NOT NULL AUTO_INCREMENT,
  `name` VARCHAR(64),
  PRIMARY KEY (`id`)
);


the first time i genrate sql, then if I, let's say, edit another table in another session, I find in the produced sql for the same table:

Code: Select all

DROP TABLE IF EXISTS `tables`;
CREATE TABLE `tables` (
  `id` INT(11) AUTO_INCREMENT,
  `name` VARCHAR(64),
  PRIMARY KEY (`id`)
);


Is it normal?
Hoping this better explains my observation.

Best regards.

[Bruno Pagès]

You are right there is a bug for the columns : when 'auto increment' is set the state of 'not null' isn't save in the project file corresponding to the table

Thank you for the bug report

[Bruno Pagès]

You can get in advance a corrected version of Bouml here : http://www.bouml.fr/files/Bouml_6.8.5_setup.exe

Because the "not null" indication isn't saved you have to set it again on the appropriate columns of the tables (when they are also "auto increment").

Best regards,

Bruno Pagès

[Bruno Pagès]

The release 6.8.5 is available, correcting this bug