Version of visual studio: 8.0.3 (build 14) Visual Studio 2019
Open the Bet solution and run the project to test on localhost.
https://docs.google.com/presentation/d/1gu-lvGkOomA0BY5btKEcldfb4jXGg0vOIc8NAJI0U50/edit?usp=sharing
See the home directory and the document titled Final-report.docx
- Print/display records from your database/tables
- Bet/Controller/ApiControllers/
- Bet/Controller/HomeController.cs
- These classes query and pass data to the Views on the front end
- Query for data/results with various parameters/filters
- Picks page and Games page query and show data with filters available from the dropdown menu
- Create a new record
- Register, Login, and make a pick from the Games page
- Delete records (soft delete function would be ideal)
- Remove pick and delete account
- Update records
- Edit pick from the Picks page
- Make use of transactions (commit & rollback)
- Making multiple picks at once from the Games page implements transactions
- Generate reports that can be exported (excel or csv format)
- Export your picks from the Picks page
- One query must perform an aggregation/group-by clause
- The settings page allows you to count the number of time you've picked a certain team
- One query must contain a sub-query
- The get method in the GameApiController.cs uses a sub query to get the games for a specific team
- Two queries must involve joins across at least 3 tables
- PickApiController.cs and HomeController.cs both have queries with 4 joins
- Enforce referential integrality (Constraints)
- There are necessary foreign key constraints on all tables
- Include Database Views, Indexes
- Indices are on all the tables to help speed up queries with certain where clauses. For example, there is an index on the name attribute for the teams table.
- Stored procedures
- The register query and the login authentication use stored procedures that pass in the proper parameters.