Connections database table
From TaskDepender
(→Connect) |
(→Connect) |
||
| Line 43: | Line 43: | ||
Taking these considerations into account means that the easiest way to add the clones will probably be to check the adjusted <tt>Connections</tt> table and to see for which connections no clones are present and then create a clone for each one of these. This is done as described in the following. | Taking these considerations into account means that the easiest way to add the clones will probably be to check the adjusted <tt>Connections</tt> table and to see for which connections no clones are present and then create a clone for each one of these. This is done as described in the following. | ||
| − | So, the first thing the SQL statement would use is a list of all the connections for which the <tt>Id</tt> is not | + | So, the first thing the SQL statement would use is a list of all the connections for which the <tt>Id</tt> is not in<ref name="not_in">[http://www.sqlite.org/lang_expr.html#in_op The IN and NOT IN operators - SQLite reference]</ref> the selection of the of the <tt>ConnectionId</tt> from the [[Deliverables database table|deliverables table]]. From the SQLite specification<ref name="single_source">[http://www.sqlite.org/syntaxdiagrams.html#single-source Single-source syntax diagram - SQLite syntax specification]</ref> it can be seen that the resulting table can be used. The syntax diagram is given in the figure below for reference. |
[[Image:Single_source_syntax_diagram.gif]] | [[Image:Single_source_syntax_diagram.gif]] | ||
