<li>Use a primary key for each table (a junction table should get a two-column primary key if each pairing should happen at most once)</li>
<li>Use a primary key for each table (a junction table should get a two-column primary key if each pairing should happen at most once)</li>
<li>Declare foreign key constraints where appropriate</li>
<li>Declare foreign key constraints where appropriate (recall that you will want to issue the <code>PRAGMA foreign_keys = ON;</code> command before using foreign keys)</li>
<li>Declare an index for the SpotterID foreign key column of Sightings</li>
<li>Declare an index for the SpotterID foreign key column of Sightings</li>
</ul>
</ul>
</li>
</li>
@ -61,7 +61,7 @@
<li>
<li>
Include the following delete command:
Include the following delete command:
<ul>
<ul>
<li>Delete a given spotter by ID and NULL out his/her ID in all of the associated sightings. Do this as a transaction and specify OR ROLLBACK for the commands therein.</li>
<li>Delete a given spotter by ID and NULL out his/her ID in all of the associated sightings. Do this as a transaction and specify OR ROLLBACK for the UPDATE command therein. I would do the same for the DELETE command, but OR ROLLBACK is not supported for DELETE in Sqlite because foreign key constraints are not checked by Sqlite's OR ROLLBACK algorithm, and - as far as I can tell - <ahref="https://www.sqlite.org/lang_conflict.html">none of the other checks performed are relevant to DELETE</a>.</li>
</ul>
</ul>
</li>
</li>
</ul>
</ul>
@ -70,7 +70,7 @@
<p>Note that in real life, it would likely be useful to have a geospatial index on latitude and longitude. SQLite doesn't support this, but there are <ahref="https://www.gaia-gis.it/fossil/libspatialite/index">add-ons</a> and <ahref="https://www.linkedin.com/pulse/what-geospatial-index-gaurav-pandey">workarounds</a> (though that is not required for this assignment).</p>
<p>Note that in real life, it would likely be useful to have a geospatial index on latitude and longitude. SQLite doesn't support this, but there are <ahref="https://www.gaia-gis.it/fossil/libspatialite/index">add-ons</a> and <ahref="https://www.linkedin.com/pulse/what-geospatial-index-gaurav-pandey">workarounds</a> (though that is not required for this assignment).</p>
<hr>
<hr>
<p>Submit a text document with all of your SQL commands in Educat, by November 6, 2024.</p>
<p>Submit a text document with all of your SQL commands in Educat, by November 13, 2024.</p>
Complete SQL commands as directed in the <ahref="Homework\01\index.html">assignment writeup</a>. Submit your work in Educat.
</td>
</tr>
<tr>
<tdclass="center top">Wednesday 11/6/2024</td>
<tdclass="center top">In class: refactor the code</td>
<tdclass="center top">20 points</td>
<tdclass="top">
In a small group, refactor the .java code from the repo to increase cohesion and decrease coupling: <pre>notes\Day 38 (class and function design)\Improve the design</pre>Show me your work to get credit on this one.
