Project

General

Profile

Actions
Copy link

Bug #1937

open

LDV online uploads the main database schema incorrectly

Added by Evgeny Novikov over 12 years ago. Updated over 12 years ago.

Status:
Open
Priority:
Normal
Assignee:
Evgeny Novikov
Category:
LDV-Online (the web service)
Start date:
10/25/2011
Due date:
% Done:

0%

Estimated time:
Detected in build:
svn
Platform:
Published in build:

Description

It seems that it just joins strings of a statement together, so

ENGINE = InnoDB
DEFAULT CHARACTER SET = utf8

leads to 
ENGINE = InnoDBDEFAULT CHARACTER SET = utf8

that leads to errors:
Logger: DEBUG: execute:"CREATE  TABLE IF NOT EXISTS `results_kb_calculated` (  `trace_id` INT(10) UNSIGNED NOT NULL ,  `Verdict` ENUM('False positive', 'True positive', 'Unknown', 'Inconclusive') NOT NULL DEFAULT 'Unknown' ,  `Tags` TEXT NULL DEFAULT NULL ,  PRIMARY KEY (`trace_id`) ,  INDEX `fk_results_kb_calculated_1` (`trace_id` ASC) ,  CONSTRAINT `fk_results_kb_calculated_1`    FOREIGN KEY (`trace_id` )    REFERENCES `traces` (`id` )    ON DELETE CASCADE    ON UPDATE NO ACTION)ENGINE = InnoDBDEFAULT CHARACTER SET = utf8COLLATE = utf8_general_ci"                                                                           
java.sql.BatchUpdateException: Unknown table engine 'InnoDBDEFAULT'                                                           
        at com.mysql.jdbc.StatementImpl.executeBatch(StatementImpl.java:1068)                                                 
        at org.linuxtesting.ldv.online.db.SQLRequests.initDBTables(SQLRequests.java:82)                                       
        at org.linuxtesting.ldv.online.db.StorageManager.initDB(StorageManager.java:121)                                      
        at org.linuxtesting.ldv.online.db.StorageManager.initStatsDB(StorageManager.java:105)                                 
        at org.linuxtesting.ldv.online.db.StorageManager.init(StorageManager.java:146)                                        
        at org.linuxtesting.ldv.online.RunLDV.main(RunLDV.java:48)

Actions
Copy link
 #1

Updated by Evgeny Novikov over 12 years ago

  • Assignee deleted (Pavel Shved)
Actions
Copy link
 #2

Updated by Evgeny Novikov over 12 years ago

The worst thing is that ldv-online reports that all is ok and continues its work that after all leads to tricky problems.

Actions
Copy link
 #3

Updated by Evgeny Novikov over 12 years ago

  • Priority changed from High to Normal

I guess that this issue isn't so important.

Actions
Copy link
 #4

Updated by Evgeny Novikov over 12 years ago

  • Status changed from New to Open
  • Assignee set to Evgeny Novikov

Should be done during ldv online refactoring.

Actions
Copy link
 #5

Updated by Evgeny Novikov over 12 years ago

I had to use so workaround:

mysql -uldv_user -p ldv < /home/ldv/ldv-tools/ldv-manager/results_schema.sql

Actions
Copy link

Also available in: Atom PDF