Problems With The "table Data" Grid And Modifying Data

[jostos]

I have a table with the following structure:

CREATE TABLE `revdef` (

`IdRev` INT(10) UNSIGNED NOT NULL AUTO_INCREMENT,

`NomRev` VARCHAR(40) NOT NULL DEFAULT '',

`DescripRev` TEXT NOT NULL,

`TablasRev` VARCHAR(20) NOT NULL DEFAULT '',

`Params` TEXT NOT NULL,

`TipoSel` TINYINT(3) UNSIGNED NOT NULL DEFAULT '1',

`Filtro` TEXT NOT NULL,

`IndGenera` CHAR(1) NOT NULL DEFAULT 'N',

`NomArchXls` VARCHAR(250) NOT NULL DEFAULT '',

`ArchXLS` LONGBLOB NOT NULL,

`TotProd` INT(10) UNSIGNED NOT NULL DEFAULT '0',

`TotEqProd` INT(10) UNSIGNED NOT NULL DEFAULT '0',

`TotEqPrec` INT(10) UNSIGNED NOT NULL DEFAULT '0',

`TotProdConv` INT(10) UNSIGNED NOT NULL DEFAULT '0',

`UsrAlta` CHAR(3) NOT NULL DEFAULT '',

`FechaAlta` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00',

`FechaIni` DATE NOT NULL DEFAULT '0000-00-00',

`FechaPlan` DATE NOT NULL DEFAULT '0000-00-00',

`FechaFin` DATE DEFAULT NULL,

`Status` TINYINT(3) UNSIGNED NOT NULL DEFAULT '1',

`UsrSuperv` CHAR(3) NOT NULL DEFAULT '',

`UsrCamb` CHAR(3) NOT NULL DEFAULT '',

`FechaCamb` DATETIME NOT NULL DEFAULT '0000-00-00 00:00:00',

PRIMARY KEY (`IdRev`)

) TYPE=MYISAM

Problem:

When I display the “Table Data” grid it displays the value of the field “NomRev” as (Binary/Image), which is incorrect.

Feature request:

If I try to modify the value of ANY field of this table, I get the following message:

“The row contains binary data that will make it unsafe to UPDATE this row from the GRID. The operation will not be performed.”

Although this is literally true, it should not be to dificult to implement the ability to modify any field EXCEPT BLOB fields.

1) Determine which fields actually changed

2) Use the primary key for the update.

For example, if only the fields “TablasRev” and “TotProd” changed, it should generate the following update code which would be safe to execute

UPDATE revdef

Set TablasRev=:TablasREv, TotProd=:TotProd // ONLY the changed fields

WHERE IdRev=:Old_IdRev // Use Primary key to identify exact record

I hope this can be implemented because not being able to modify ANY data is VERY Inconvenient.

Regards

jostos

<_<

[nithin]

Hello,

Thanks for posting, and its a valid request.

Currently while UPDATE we are SETting all column values, and use the PK column in WHERE clause if its present, otherwise use all columns in WHERE clause.

We should SET only column(s) those are edited, in UPDATE clause .

I added this to issue tracker

http://code.google.com/p/sqlyog/issues/detail?id=1063

We will look into this issue after 8.1 GA released and update the status here(probably next week).

Regards

Nithin

[peterlaursen]

The workaround is to execute a SELECT query not including binary columns (and not columns with spatial data either) and do operations from RESULT tab.

[navyashree.r]

Issue fixed internally and will be available in next 8.13 beta release probably Monday.

Thank You.

Regards,

Navya

[navyashree.r]

Hi,

This issue is fixed and available in 8.13 beta2, publicly available!

Please refer to:

http://www.webyog.com/blog/2009/07/15/sqly…-been-released/

Please let us know the status.

Thank you.

Regards,

Navya

[Author]

Posts