forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Bug: Creating Table With Guy Ignores Columns After An Empty Line
- This topic is empty.
-
AuthorPosts
-
-
May 2, 2006 at 10:21 am #9664TomBezMember
Hi there,
when trying to create a table and you hit the insert button cause you forgot a column than there are inserted 2 lines (instead of the expected 1 line). after inserting the line (column) and hitting the create table button I first noticed, that if you have an empty line between the columndefinitions, all definitions after this empty line are withdrawn. this does not happen when altering a table (there you can have empty lines, without a problem).
bug occures in 5.02 and 5.11
regards, tom
-
May 2, 2006 at 6:50 pm #21519peterlaursenParticipant
Confirmed and reproduced with 5.12 beta 3 too.
-
May 3, 2006 at 7:58 am #21520RiteshMember
This is a known and expected behavior and not a bug. SQLyog checks for the first empty row and stops. If you notice that the CREATE TABLE GRID is always initialized with more rows then what is required for the table creation.
SQLyog basically checks for the first empty row and stops.
-
May 3, 2006 at 8:07 am #21521peterlaursenParticipant
@Ritesh .. I don't think you understand!
Try:
Create two columns, highligt 2nd column and click the 'insert' button. TWO (and not one) empty rows are created in grid between 1st and 2nd row. This is a GUI bug in my opinion.
I accept that it stops generating columns for the 'create statement' when parsing and meeting an empty row in the grid!
-
May 3, 2006 at 8:37 am #21522vygiMemberpeterlaursen wrote on May 3 2006, 08:07 AM:Create two columns, highligt 2nd column and click the 'insert' button. TWO (and not one) empty rows are created in grid between 1st and 2nd row. This is a GUI bug in my opinion.
Heya,
I always wanted to submit this bug (yes, it is clearly a BUG to me), just did not have time.
Once I've started to create a quite big table and after I had 15 ot 20 rows I tried to insert one right after the first row. I've got two instead like reported here. Then I don't remember what I did exactly but as result I've lost everything as only one column was created in the table.
-
May 3, 2006 at 9:37 am #21523RiteshMember
Bug reproduced and confirmed. Will be fixed in BETA 4 development tree.
-
May 3, 2006 at 9:50 am #21524TomBezMemberRitesh wrote on May 3 2006, 11:37 AM:Bug reproduced and confirmed. Will be fixed in BETA 4 development tree.
maybe you could also make a trim on the table grid, to get rid of all empty rows. this would reduce confusion, and there is a delete button, so there is no real use of stopping at an empty grid-row (maybe it would be better, to make the grid behavior just the same, as it is when inserting data into a table).
-
May 3, 2006 at 10:01 am #21525peterlaursenParticipantCode:there is no real use of stopping at an empty grid-row
You will have to stop it somehow if it shall not run forever ….
Basically INSERTION of rows is implemented differently in CREATE TABLE and ALTER TABLE. In ALTER TABLE you must click INSERT, in CREATE TABLE you just move cursor to next empty row.
I think it is not the time to change that now!
-
May 4, 2006 at 2:33 am #21526
-
-
AuthorPosts
- You must be logged in to reply to this topic.