Forum Replies Created
-
AuthorPosts
-
peterlaursen
ParticipantSorry .. I misunderstood. I thought it was about Data Sync.
March 27, 2015 at 8:55 am in reply to: Database Treeview Shows Same [email protected] In Every Connection Tab #35262ParticipantYes, it does! What else should it display?
ParticipantWhy is it difficult? With “table type”, do you mean “table engine”?
All meta-information about tables is displayed in the INFO tab.
ParticipantCurrently you can create a batch job – refer http://faq.webyog.com/content/27/35/en/can-i-execute-more-sja-jobs-at-the-same-time.
You can create one job file in the wizard and simply edit target connection details for the rest in an editor.
ParticipantIf indexes or not makes a difference on what result set is returned, it is a bug with the server.
Indexes should only matter for performance of the query and the amont of memory the server uses when executing the query – not the result. If it is reproducible on a current server version, I think you should post a bug (with a test case suffiient to reproduce) to bugs.mysql.com
ParticipantWhy do you think this is an issue with SQLyog? it is the MySQL server that executesthequery and returns the result set. Please try n another client (‘mysql’ command line, phpMyAdmin or whatever you have acces to) and check here.
I think it would bemore appropriate tor eport this to bugs.mysql.com, if you think it is a bug in the server: And you should always mention the server version in such reports BTW.
You are of course welcome to ask users of our Forums (and us). But we would need a full test case with table structure and data to verify. And in principle we support or own programs and not the MySQl server.
ParticipantTry (assuming that it is OK that you lose the data in the corrupted tables)
1) execute “DROP TABLE tablename;” from the SQLyog editor. You may of course also try to repair them first (“REPAIR TABLE tablename;”). Ensure the correct defaltdatabase (exectuea USE statement or select the database in SQLyo Object browser.
2) If tables are MyISAM tabs and if you have access to the file system on the server, delete or rename files “tablename.frm”, “tablename.MYD” and “tablename.MYI” for affected tables. DO NOT attempt something similar with InnoDB tables!
3) Dump the entire database, DROP the database and reimport the dump. Dependng on what exactly the problem is, this could ‘clean up’ hidden tables (as they will most likely not be included in the dump).
if you have access to do so, I suggest that you stop the MySQL server and make a copy of the complete data folder first.
Any idea how the tables could corrupt like that?
ParticipantYou cannot import such fiiles with any client tools. Only the server can read those. You should NEVER copy such files from the server data folder. They are useless when moved from there. This applies to InnoDB files in particular. MyISAM files can be copied in most cases though it is not recommended.
You will need to connect to the server from where you copied the files and then export/dump the table. The resulting SQL DUMP -file can be imported from SQLyog ‘tools’ menu .. execute SQL script
ParticipantYou can read this about the Scehma Designer in SQLyog: http://sqlyogkb.webyog.com/category/266-schema-designer
ParticipantMore precisely SHOW FULL FIELDS does not have any information about the storage engine. So we assume *worst case* for strings (what was utf8 – using up to 3 bytes per character – before utf8mb4 was introduced). We should probably query I_S about the storage engine for the column or completely change the logic.
The whole code dates back to MySQL 3.23/4.0 -dasy before unicode was introduced and I_S did not exist. The only change ws taht with MySQL 4.1 we added the worst case* assumption. Code/logicis museum-worthy relly
ParticipantSo the char/varchar issue is inherited from MySQl. The decimal issue looks like a bug in SQLyog.
ParticipantFor “Export as SQL” we don’t execute SHOW CREATE TABLE but SHOW FULL FIELDS FROM ..
Try “SHOW FULL FIELDS FROM `bma600`;”
Field Type Collation Null Key Default Extra Privileges Comment
BLQ_NOSSO_NUM decimal(18,0) (NULL) YES (NULL) select,insert,update,references
BLQ_DIG_NOS_NUM char(6) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_TAM_NN decimal(2,0) (NULL) YES (NULL) select,insert,update,references
BLQ_COD_BCO decimal(4,0) (NULL) YES (NULL) select,insert,update,references
BLQ_DIG_BCO decimal(2,0) (NULL) YES (NULL) select,insert,update,references
BLQ_COD_AGE decimal(5,0) (NULL) YES (NULL) select,insert,update,references
BLQ_DIG_AGE decimal(2,0) (NULL) YES (NULL) select,insert,update,references
BLQ_COD_CONV decimal(19,0) (NULL) YES (NULL) select,insert,update,references
BLQ_LIN_DIG varchar(150) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_COD_BAR varchar(150) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_LOC_PAG varchar(300) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_COD_CED decimal(18,0) (NULL) YES (NULL) select,insert,update,references
BLQ_DIG_CED decimal(2,0) (NULL) YES (NULL) select,insert,update,references
BLQ_CNPJ_CED decimal(16,0) (NULL) YES (NULL) select,insert,update,references
BLQ_NOME_CED varchar(120) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_DT_DOC decimal(9,0) (NULL) YES (NULL) select,insert,update,references
BLQ_DT_PROC decimal(9,0) (NULL) YES (NULL) select,insert,update,references
BLQ_DT_VEN decimal(9,0) (NULL) YES (NULL) select,insert,update,references
BLQ_QTD_MOE decimal(11,0) (NULL) YES (NULL) select,insert,update,references
BLQ_VALOR decimal(13,0) (NULL) YES (NULL) select,insert,update,references
BLQ_VAL_DOC decimal(13,0) (NULL) YES (NULL) select,insert,update,references
BLQ_VAL_DES decimal(13,0) (NULL) YES (NULL) select,insert,update,references
BLQ_VAL_DED decimal(13,0) (NULL) YES (NULL) select,insert,update,references
BLQ_VAL_MORA decimal(13,0) (NULL) YES (NULL) select,insert,update,references
BLQ_VAL_ACR decimal(13,0) (NULL) YES (NULL) select,insert,update,references
BLQ_VAL_COB decimal(13,0) (NULL) YES (NULL) select,insert,update,references
BLQ_TPO_INS char(3) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_CNPJ_CPF_SAC decimal(16,0) (NULL) YES (NULL) select,insert,update,references
BLQ_NOME_SAC varchar(120) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_END_SAC varchar(120) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_BAI_SAC varchar(90) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_CEP_SAC decimal(6,0) (NULL) YES (NULL) select,insert,update,references
BLQ_CCEP_SAC decimal(4,0) (NULL) YES (NULL) select,insert,update,references
BLQ_CID_SAC varchar(90) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_EST_SAC varchar(6) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_NUM_DOC decimal(11,0) (NULL) YES (NULL) select,insert,update,references
BLQ_ESP_DOC varchar(6) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_ACEITE char(3) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_USO_BCO varchar(75) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_COD_CART decimal(4,0) (NULL) YES (NULL) select,insert,update,references
BLQ_MOEDA varchar(9) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_NOME_AVAL varchar(120) utf8_general_ci YES (NULL) select,insert,update,references
BLQ_COD_EMP decimal(6,0) (NULL) YES (NULL) select,insert,update,references
BLQ_COD_POR decimal(6,0) (NULL) YES (NULL) select,insert,update,references
BLQ_PER_MULTA decimal(7,0) (NULL) YES (NULL) select,insert,update,references
BLQ_COD_EST decimal(4,0) (NULL) YES (NULL) select,insert,update,references
BLQ_OBS_RET varchar(765) utf8_general_ci YES (NULL) select,insert,update,referencesParticipantsomething is crazy! If Import your sql and export again I get
SQLyog Ultimate v12.09 (64 bit)
MySQL – 5.6.23-log**********************************************************************//*!40101 SET NAMES utf8 */;create table `bma600` (`BLQ_NOSSO_NUM` Decimal (19),`BLQ_DIG_NOS_NUM` char (18),`BLQ_TAM_NN` Decimal (3),`BLQ_COD_BCO` Decimal (5),`BLQ_DIG_BCO` Decimal (3),`BLQ_COD_AGE` Decimal (6),`BLQ_DIG_AGE` Decimal (3),`BLQ_COD_CONV` Decimal (20),`BLQ_LIN_DIG` varchar (450),`BLQ_COD_BAR` varchar (450),`BLQ_LOC_PAG` varchar (900),`BLQ_COD_CED` Decimal (19),`BLQ_DIG_CED` Decimal (3),`BLQ_CNPJ_CED` Decimal (17),`BLQ_NOME_CED` varchar (360),`BLQ_DT_DOC` Decimal (10),`BLQ_DT_PROC` Decimal (10),`BLQ_DT_VEN` Decimal (10),`BLQ_QTD_MOE` Decimal (12),`BLQ_VALOR` Decimal (14),`BLQ_VAL_DOC` Decimal (14),`BLQ_VAL_DES` Decimal (14),`BLQ_VAL_DED` Decimal (14),`BLQ_VAL_MORA` Decimal (14),`BLQ_VAL_ACR` Decimal (14),`BLQ_VAL_COB` Decimal (14),`BLQ_TPO_INS` char (9),`BLQ_CNPJ_CPF_SAC` Decimal (17),`BLQ_NOME_SAC` varchar (360),`BLQ_END_SAC` varchar (360),`BLQ_BAI_SAC` varchar (270),`BLQ_CEP_SAC` Decimal (7),`BLQ_CCEP_SAC` Decimal (5),`BLQ_CID_SAC` varchar (270),`BLQ_EST_SAC` varchar (18),`BLQ_NUM_DOC` Decimal (12),`BLQ_ESP_DOC` varchar (18),`BLQ_ACEITE` char (9),`BLQ_USO_BCO` varchar (225),`BLQ_COD_CART` Decimal (5),`BLQ_MOEDA` varchar (27),`BLQ_NOME_AVAL` varchar (360),`BLQ_COD_EMP` Decimal (7),`BLQ_COD_POR` Decimal (7),`BLQ_PER_MULTA` Decimal (8),`BLQ_COD_EST` Decimal (5),`BLQ_OBS_RET` varchar (2295));So first row 17,0 becomes 18 becomes 19 .. “But if I use “Backup as SQL-dump” I get (2nd time)CREATE TABLE `bma600` (`BLQ_NOSSO_NUM` decimal(18,0) DEFAULT NULL,`BLQ_DIG_NOS_NUM` char(6) DEFAULT NULL,`BLQ_TAM_NN` decimal(2,0) DEFAULT NULL,`BLQ_COD_BCO` decimal(4,0) DEFAULT NULL,`BLQ_DIG_BCO` decimal(2,0) DEFAULT NULL,`BLQ_COD_AGE` decimal(5,0) DEFAULT NULL,`BLQ_DIG_AGE` decimal(2,0) DEFAULT NULL,`BLQ_COD_CONV` decimal(19,0) DEFAULT NULL,`BLQ_LIN_DIG` varchar(150) DEFAULT NULL,`BLQ_COD_BAR` varchar(150) DEFAULT NULL,`BLQ_LOC_PAG` varchar(300) DEFAULT NULL,`BLQ_COD_CED` decimal(18,0) DEFAULT NULL,`BLQ_DIG_CED` decimal(2,0) DEFAULT NULL,`BLQ_CNPJ_CED` decimal(16,0) DEFAULT NULL,`BLQ_NOME_CED` varchar(120) DEFAULT NULL,`BLQ_DT_DOC` decimal(9,0) DEFAULT NULL,`BLQ_DT_PROC` decimal(9,0) DEFAULT NULL,`BLQ_DT_VEN` decimal(9,0) DEFAULT NULL,`BLQ_QTD_MOE` decimal(11,0) DEFAULT NULL,`BLQ_VALOR` decimal(13,0) DEFAULT NULL,`BLQ_VAL_DOC` decimal(13,0) DEFAULT NULL,`BLQ_VAL_DES` decimal(13,0) DEFAULT NULL,`BLQ_VAL_DED` decimal(13,0) DEFAULT NULL,`BLQ_VAL_MORA` decimal(13,0) DEFAULT NULL,`BLQ_VAL_ACR` decimal(13,0) DEFAULT NULL,`BLQ_VAL_COB` decimal(13,0) DEFAULT NULL,`BLQ_TPO_INS` char(3) DEFAULT NULL,`BLQ_CNPJ_CPF_SAC` decimal(16,0) DEFAULT NULL,`BLQ_NOME_SAC` varchar(120) DEFAULT NULL,`BLQ_END_SAC` varchar(120) DEFAULT NULL,`BLQ_BAI_SAC` varchar(90) DEFAULT NULL,`BLQ_CEP_SAC` decimal(6,0) DEFAULT NULL,`BLQ_CCEP_SAC` decimal(4,0) DEFAULT NULL,`BLQ_CID_SAC` varchar(90) DEFAULT NULL,`BLQ_EST_SAC` varchar(6) DEFAULT NULL,`BLQ_NUM_DOC` decimal(11,0) DEFAULT NULL,`BLQ_ESP_DOC` varchar(6) DEFAULT NULL,`BLQ_ACEITE` char(3) DEFAULT NULL,`BLQ_USO_BCO` varchar(75) DEFAULT NULL,`BLQ_COD_CART` decimal(4,0) DEFAULT NULL,`BLQ_MOEDA` varchar(9) DEFAULT NULL,`BLQ_NOME_AVAL` varchar(120) DEFAULT NULL,`BLQ_COD_EMP` decimal(6,0) DEFAULT NULL,`BLQ_COD_POR` decimal(6,0) DEFAULT NULL,`BLQ_PER_MULTA` decimal(7,0) DEFAULT NULL,`BLQ_COD_EST` decimal(4,0) DEFAULT NULL,`BLQ_OBS_RET` varchar(765) DEFAULT NULL) ENGINE=InnoDB DEFAULT CHARSET=utf8;Two problems here
1) decimal length increments by one. This we have never noticed before. We will check why it happens.
2) char/varchar length gets multiplied with 3. This a known issue if charset is UTF8. The statement we use for “export as SQL” returns the *byte-length* – not the *character length*. I don’t remember internals right now. But I remember clearly that I filed a bug report to MySQL about it.
Actually we only introduced “Export as SQL” very reluctantly many years agp. phpMyAdmin has/had the same and it was a massive request by users taht SQLyog should have exactly the same opton. Maybe we should change it so that it executes SHOW CREATE TABLE. But .. but .. please let us check internals and see if can we can remember something from old days.
Is it posible that you could use “Backup as SQL-dump” for as long?
Participant“Couldn’t you just send the encrypted license key to your customer portal”. No this isnot possble. A user is identifed by the email address registered with the license.
ParticipantI have replied in the ticket you have created.
-
AuthorPosts
