Ensure current API code is using PostgreSQL to retrieve requested data about team-budget HOT 5 CLOSED

Based on my testing today with the "secrets" branch, I concluded that when we replaced sqlite3 with AWS-postgreSQL, the API must have been pulling data from postgres and not a local sqlite instance. I may be wrong, and looking at the existing code I don't know how that would work exactly, but I am puzzled by the fact that I wiped out the reference to sqlite3 in settings.py and I was still able to get a response from each endpoint and that the response included all the data I expected to see.

To be tested: what happens when I break the project_config.py (e.g. give it a bad database password).

from team-budget.

@MikeTheCanuck the version that you're testing with may still be pulling data from the CSV files

from team-budget.

The two endpoints OCRB and KPM are still getting data from the CSV files. However, the summary endpoint gets its data from the database. I just tested pull request #35 and confirmed that the endpoint can draw data from the AWS EC2 instance of PostgreSQL, rather than the sqlite3 that I used originally during development of that summary endpoint.

from team-budget.

I would leave this issue open until we have refactored the endpoints, so that OCRB and KPM get their data from the database, rather than reading from the CSV file. At that point, we can probably get rid of the summary endpoint, which is similar to OCRB, although it shows one way to do filtering and sorting, which goes beyond the current functionality of OCRB.

from team-budget.

Closed by the merge of pull request #59. All endpoints now read data from whichever database is specified in the project_config.py file. I tested with the AWS EC2 instance running PostgreSQL and also tested with the configuration set for the embedded sqlite3 database. They both worked. Not at the same time, of course. But you can change the project_config.py and restart the server to access a different database.

from team-budget.