i´m not using fork e.g.
there is no code excluded. because it´s not necessary to implement not working code ;-)
CREATE TABLE `table_1` (<br>
`ID` int(11) NOT NULL AUTO_INCREMENT,<br>
`version` varchar(200) NOT NULL,<br>
`filename` varchar(200) NOT NULL,<br>
`size` int(11) DEFAULT NULL,<br>
`MD5_checksum` varchar(200) DEFAULT NULL,<br>
`release_notes` varchar(200) NOT NULL,<br>
`remark` varchar(2000) DEFAULT NULL,<br>
`rec_level` int(11) NOT NULL,<br>
`date_rec_green` date DEFAULT NULL,<br>
`date_rec_yellow` date DEFAULT NULL,<br>
`date_rec_red` date DEFAULT NULL,<br>
`date_compl_green` date DEFAULT NULL,<br>
`date_comp_yellow` date DEFAULT NULL,<br>
`date_compl_red` date DEFAULT NULL,<br>
`os_type` int(11) DEFAULT NULL,<br>
`feature_set` int(11) DEFAULT NULL,<br>
PRIMARY KEY (`ID`),<br>
UNIQUE KEY `ID_UNIQUE` (`ID`),<br>
KEY `fk_firmware_rec_level` (`rec_level`),<br>
KEY `fk_firmware_os_type` (`os_type`),<br>
KEY `fk_firmware_feature_set` (`feature_set`),<br>
CONSTRAINT `fk_firmware_feature_set` FOREIGN KEY (`feature_set`) REF
+ERENCES <br>`nl_firmware_feature_set` (`ID`) ON DELETE NO ACTION ON U
+PDATE NO ACTION,<br>
CONSTRAINT `fk_firmware_os_type` FOREIGN KEY (`os_type`) REFERENCES
+<br>`nl_firmware_os_type` (`ID`) ON DELETE NO ACTION ON UPDATE NO ACT
+ION,<br>
CONSTRAINT `fk_firmware_rec_level` FOREIGN KEY (`rec_level`) REFEREN
+CES <br>`nl_firmware_rec_level` (`ID`) ON DELETE NO ACTION ON UPDATE
+NO ACTION<br>
) ENGINE=InnoDB AUTO_INCREMENT=11 DEFAULT CHARSET=utf8$$<br>
i´m completly new to this topic for this i hope that this is the scheme that helps a lil...
$perlig =~ s/pec/cep/g if 'errors expected';
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.