forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Can't Edit Enum
- This topic is empty.
-
AuthorPosts
-
-
January 11, 2007 at 5:09 am #23219
peterlaursen
Participantbug 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 #23220
dbr1066
MemberThanks 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 #23221
peterlaursen
ParticipantWe 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 #23222
peterlaursen
ParticipantThis 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 #23223
dbr1066
Memberpeterlaursen 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.