Actions
Feature #1244
closedinit_db option
Status:
Closed
Priority:
Low
Assigned To:
-
Category:
-
Start date:
01/14/2011
Due date:
% Done:
100%
Estimated time:
Description
When you launch tm_server without options, we have this output :
Device_params: fin de creation of device_type;string_type;0;device Device_params: fin de creation of id;integer_type;2;0 Device_params: fin de creation of name;string_type;1;name Device_params: fin de creation of color;color_type;3;red Device_params: fin de creation of father;integer_type;4;0 Device_params: fin de creation of status;status_type;5;off Topology_Manager: Initialize Topology Manager 0 Usage : ./tm_server [--option=value] Options : - init_db : Create the tables into the mysql DB. All precedent data in the tables are lost. The values are: yes or no Example: ./tm_server --init_db=yes
What is the default value ?
Is this option mandatory or not ?
You should precise the message perhaps.
Updated by Guevara Luz over 14 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
In the version 51 this bug has been fixed. When you launch the tm_server without options the existent database will be kept. If you want to loss the existent database, you must to specify the "--init_db_with=PATH_XML_FILE", where PATH_XML_FILE is the path to the hardware_tree.xml file.
Updated by Dosme Nicolas almost 13 years ago
- Status changed from Resolved to Closed
Actions