Default values error in 'Column Properties' dialog

AthenaOfDelphi · Post by **AthenaOfDelphi** » Sun 11 Jul 2010 12:28

Hi,

I've recently (in the last few days) updated to version 4.50.285 of dbForge Studio for MySQL and I'm experiencing a real problem with the Column Properties dialog.

I'm currently developing a database using the diagram editor and when I edit a column (either by double clicking the table to edit through the table properties dialog or double clicking a column to edit through the column properties dialog), if I have a default value set for BIGINT and SMALLINT fields (I've not tried any others), the default value comes back through the dialog as 'System.Byte[]'.

It doesn't occur if the default value is NULL.

When you try and save the changes, these strange default values are posted through to the server which obviously results in a failure.

For me, the steps to reproduce are:-

Create a new diagram
Create a new table on the diagram
Link the table to an active database and provide it with a name
Create a single field in the table of type 'BIGINT' and set the default value to 0
Save the table
Double click the table header to open the table properties dialog
Double click the field

When I do this, the field's default value is 'System.Byte[]'.

I'm running on Windows XP Pro Version 2002 SP 3. My local MySQL server is 4.1.22-community-nt. The machine itself is fully patched with all available updates for things like .net and other core system elements.

If you need more information, please don't hesitate to get in touch.

AthenaOfDelphi · Post by **AthenaOfDelphi** » Sun 11 Jul 2010 12:36

An extra nugget of information...

I've just noticed that this invalid default value is also being displayed in the property inspector whenever one of my integer fields with a default other than null is selected.

The problem also isn't limited to integer fields. I've just created a string field with the default blahblah (which incidentally won't save without single quotes around it). This is displayed as 'System.Byte[]' (including the quotes).

Alexz · Post by **Alexz** » Mon 12 Jul 2010 07:46

Thank you for detailed description about the problem. It occures only on MySQL servers 4.1. We fixed it. The new build will be available in a week.

AthenaOfDelphi · Post by **AthenaOfDelphi** » Mon 12 Jul 2010 09:53

Alexz wrote:Thank you for detailed description about the problem. It occures only on MySQL servers 4.1. We fixed it. The new build will be available in a week.

Well, if you'd like a user to test it, I'm desperate for a fixed version as I'm using it alot at the moment, designing a database for a new project so it's a real headache

Anyhow, thanks guys for the speedy turnaround and response. It's much appreciated

AthenaOfDelphi · Post by **AthenaOfDelphi** » Fri 16 Jul 2010 10:16

Any news?

I don't want to nag or complain about this issue, but is there any news on progress (or a fixed version I can test) as it actually has wider implications than just maintaining the tables.

I'm currently unable to synchronise schema's as the 'System.Byte[]' is dropping into the synchronisation scripts generated by the application.

.jp · Post by **.jp** » Fri 16 Jul 2010 13:18

Sorry for the delay.
Unfortunately we haven't released the new build yet because there are problems which should be fixed before the release.
We will notify you as soon as the new build of dbForge Studio for MySQL is available for download.

.jp · Post by **.jp** » Mon 26 Jul 2010 14:19

AthenaOfDelphi wrote:Any news?

A new build (4.50.300) of dbForge Studio for MySQL is available for download. Thank you for your patience.

AthenaOfDelphi · Post by **AthenaOfDelphi** » Mon 26 Jul 2010 15:41

I've just downloaded and tested using the column properties dialog. I've not tried a schema comparison yet, but so far so good.

Thanks