forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Can't Edit Enum
- This topic is empty.
-
AuthorPosts
-
-
January 10, 2007 at 4:40 pm #10122dbr1066Member
Hello,
I'm testing SqlYog 5.21. One of the common tasks I need to do is query the database for fields that are blank, and edit the results. I have a table like this:
CREATE TABLE `mytable` (
`ID` mediumint(6) unsigned NOT NULL auto_increment,
`FieldA` decimal(9,7) NOT NULL default '0.0000000',
`FieldB` decimal(9,7) NOT NULL default '0.0000000',
`FieldC` enum('','A','B','B1','B2','C','C1') NOT NULL,
I run a query using the 'Execute and Edit Result Set' command, like this
SELECT * FROM mytable WHERE FieldC = '' (find all the rows in FieldC that have no value)
In the result set, there are no values showing in the drop down menu for FieldC (well, that's OK, because I wanted to find all the rows with no value there!) But, the drop down Enum menu should show the enum choices for that field, shouldn't it? Mine doesn't show any choices beyond 'Null'. So, I can't assign a new value to a row using the drop down menu. And if I try to type in a new value, nothing happens (i.e. I can't type in the SqlYog result set grid, even though I ran an 'Execute and Edit Result Set query')
Am I missing something about how the editing process is supposed to work with result sets? I can edit the regular table data view fine, but its a real drag to have to troll through the table to find empty rows.
Any advice?
-
January 11, 2007 at 5:09 am #23219peterlaursenParticipant
bug confirmed!
Code:CREATE TABLE `asqw` ( `id` bigint(20) NOT NULL auto_increment, `c` enum('','a','b') NOT NULL,
PRIMARY KEY (`id`) )
ENGINE=InnoDB DEFAULT CHARSET=latin1;insert into `asqw`(`id`,`c`) values ( NULL,'a');
insert into `asqw`(`id`,`c`) values ( NULL,'b');select * from asqw where id = 1 or `c` IS NULL;
-
January 11, 2007 at 9:54 am #23220dbr1066Member
Thanks peterlaursen,
I guess I'll just have to see if this is fixed in a future release of SqlYog
-
January 11, 2007 at 10:12 am #23221peterlaursenParticipant
We will definitely fix this, and likely in next release (5.23).
Data tab is not affected and SET types are not either.
So I do not think it is a big issue.
Probably we will understand the issue in detail later today or tomorrow.
A workaround is to do things from DATA tab once.
Now you copy the SQL from HISTORY, paste into editor, edit and execute.
-
January 12, 2007 at 9:47 am #23222peterlaursenParticipant
This issue is now fixed. It will me merged into the 5.23 tree and released with beta1.
Also another issue was fixed in 'the same shot': When a ENUM or a SET was defined with “NOT NULL” the dropdown (in both DATA tab and RESULT tab) still displayed NULL as an option.
-
January 12, 2007 at 2:08 pm #23223dbr1066Memberpeterlaursen wrote on Jan 12 2007, 09:47 AM:This issue is now fixed. It will me merged into the 5.23 tree and released with beta1.
Also another issue was fixed in 'the same shot': When a ENUM or a SET was defined with “NOT NULL” the dropdown (in both DATA tab and RESULT tab) still displayed NULL as an option.
Hey, that's great! Thanks for acting so quickly to improve an already very useful product.
-
-
AuthorPosts
- You must be logged in to reply to this topic.