The current sql script for the database is attached here.
Web interface to do:
- Parameterize SQL queries to hinder SQL injection attacksStyle forms
- Slim code - figure out how to object orient and limit repetition, if this is possible?
- Link autocomplete value with database value for proper insertion
- Link each of these values & insert into activity_fact table
- Style formsParameterize SQL queries to hinder SQL injection attacks
Database to do:
- make basic ER Diagram for San Diego
- Finish data dictionary explaining each entity and attribute - after feedback
- Split series name from source table? – see how organized in GCD
- Should we have a field the interface for the data-entry user's name? if yes, where would this value go in the database?
- Otherwise, this may be covered with log-in/privileges?
...