I open a schema and choose a table and, with the new tabs interface, my columns are gone! The only way I can see my columns is in data and query views. But even then I can't see the data types and sizes so I can't edit my columns.
Help?
Column view is gone?
I'm running revision 2712 and I can't see my columns anymore!
I open a schema and choose a table and, with the new tabs interface, my columns are gone! The only way I can see my columns is in data and query views. But even then I can't see the data types and sizes so I can't edit my columns.
Help?
I open a schema and choose a table and, with the new tabs interface, my columns are gone! The only way I can see my columns is in data and query views. But even then I can't see the data types and sizes so I can't edit my columns.
Help?
![[expired user #4457]'s profile image](http://www.gravatar.com/avatar/70afbf2259b4449d8ae1429e054df1b1?d=identicon&s=48)
[expired user #4457] posted
14 years ago
Had to revert to build 2405 so I could work again. :(
[expired user #4457] posted
14 years ago
Had to revert to build 2405 so I could work again. :(
ansgar posted
14 years ago
Can't believe that - no change on the table editor between r2705 and r2712 . And also I can't reproduce it. If you're really sure about that, could you please post the CREATE TABLE statement here for that table?
[expired user #4457] posted
14 years ago
You may not believe it but it was true.
I'll see about installing on a VM and try reproducing the problem. Also I had gone from I believe r2694 directly to r2712. So I wonder if that played a part?
I'll see about installing on a VM and try reproducing the problem. Also I had gone from I believe r2694 directly to r2712. So I wonder if that played a part?
[expired user #4457] posted
14 years ago
Just upgraded from r2405 directly to r2720. Still have the same behavior. For example:
Simple table but no view of the columns at all. Hop
This screencap animation should show you what I'm talking about.
Does BBCode work here?
CREATE TABLE `jobs` (
PRIMARY KEY (`job_ID`),
UNIQUE INDEX `job_ID` (`job_ID`),
INDEX `job_ID_2` (`job_ID`, `customer_ID`, `plan_ID`)
)
COLLATE=latin1_swedish_ci
ENGINE=InnoDB
ROW_FORMAT=COMPACT
AUTO_INCREMENT=2
AVG_ROW_LENGTH=16384Simple table but no view of the columns at all. Hop
This screencap animation should show you what I'm talking about.
Does BBCode work here?
[expired user #4457] posted
14 years ago
Sorry about the double-postings. I keep hitting the back button and it posts again. 
ansgar posted
14 years ago
The only change regarding the table editor between r2694 and r2712 is r2705 . Which should not have such an effect. But it would be nice if you check if r2704 did not have this problem? Thanks!
ansgar posted
14 years ago
And could you paste the result of a
SHOW CREATE TABLE jobsAlready posted the SHOW CREATE TABLE above?
ansgar posted
14 years ago
That was the broken one which has no columns, just indexes, saw that? You need to query that SHOW CREATE TABLE so we can see the real one.
[expired user #4457] posted
14 years ago
This is the SHOW CREATE TABLE jobs result from r2405:
CREATE TABLE "jobs" (
"job_ID" bigint(20) unsigned NOT NULL AUTO_INCREMENT,
"checked_out" tinyint(1) unsigned DEFAULT '0',
"customer_ID" int(11) unsigned DEFAULT NULL,
"plan_ID" bigint(20) unsigned DEFAULT NULL,
"total_square_footage" int(10) unsigned DEFAULT NULL,
"engineering_date" date DEFAULT NULL,
"job_completed" tinyint(3) unsigned DEFAULT '0',
"job_notes" varchar(2000) DEFAULT NULL,
PRIMARY KEY ("job_ID"),
UNIQUE KEY "job_ID" ("job_ID"),
KEY "job_ID_2" ("job_ID","customer_ID","plan_ID")
)Hm that's not exactly what I meant - I assume this is taken from HeidiSQL's export to file feature? The double quotes are ANSI syntax. What I need is the very original "SHOW CREATE TABLE `jobs`" result from MySQL, using the query tab. Or am I wrong and you did exactly that?
ansgar posted
14 years ago
There was a similar bug recently resulting in an empty SHOW CREATE TABLE for broken table comments with critical characters in it. But that was fixed in r2684 . But I guess there is a problem with some regular expression parsing that SHOW CREATE TABLE result. In order to analyze that I need your original CREATE TABLE from your jobs table.
[expired user #4457] posted
14 years ago
The SHOW CREATE TABLE results above are indeed the results from the query tab in r2405.
[expired user #4457] posted
14 years ago
Our server's sql_mode is set to:
REAL_AS_FLOAT,PIPES_AS_CONCAT,ANSI_QUOTES,IGNORE_SPACE,ANSI
REAL_AS_FLOAT,PIPES_AS_CONCAT,ANSI_QUOTES,IGNORE_SPACE,ANSI
[expired user #4457] posted
14 years ago
Went to the MySQL command prompt and ran the command. This is the output directly from the MySQL server.
mysql> show create table engineering.jobs;
+-------+-----------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
-----------------------------------------------------+
| Table | Create Table
|
+-------+-----------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
-----------------------------------------------------+
| jobs | CREATE TABLE "jobs" (
"job_ID" bigint(20) unsigned NOT NULL AUTO_INCREMENT,
"checked_out" tinyint(1) unsigned DEFAULT '0',
"customer_ID" int(11) unsigned DEFAULT NULL,
"plan_ID" bigint(20) unsigned DEFAULT NULL,
"total_square_footage" int(10) unsigned DEFAULT NULL,
"engineering_date" date DEFAULT NULL,
"job_completed" tinyint(3) unsigned DEFAULT '0',
"job_notes" varchar(2000) DEFAULT NULL,
PRIMARY KEY ("job_ID"),
UNIQUE KEY "job_ID" ("job_ID"),
KEY "job_ID_2" ("job_ID","customer_ID","plan_ID")
) |
+-------+-----------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
-----------------------------------------------------+
1 row in set (0.00 sec)Our server's sql_mode is set to:
REAL_AS_FLOAT,PIPES_AS_CONCAT,ANSI_QUOTES,IGNORE_SPACE,ANSI
Aah.... makes sense now. This must cause the missing columns, as there are regular expression expecting the backtick!
ansgar posted
14 years ago
ANSI_QUOTES support added in r2727
[expired user #4457] posted
14 years ago
Thanks! I'll give r2727 a shot and let you know how it worked. 
[expired user #4457] posted
14 years ago
Pulled r2727 down and, so far at least, it's working great! :D
Please login to leave a reply, or register at first.
Database powered by MariaDB
HeidiSQL is proudly built with Embarcadero Delphi
