[Q] SQLite Bad Practice?

So I feel that I already know the answer to this question (Which is no) but I feel I should ask just in case.

I am developing my first app for android and have a question whether or not my current method of storing data in a SQLite database is considered bad practice and should be re-evaluated before I go any further.

Basically I am creating a changes tracking app. The user can specify a project and add entries for that project to track changes, ideas, etc.

The current way I am storing the data in the SQLite database is by creating an individual table for every project and then storing the entries for that project within that projects table.

This is what my question is in regards to, is it bad practice to create a separate table for each project? I realize that with enough projects my database would be overrun by tables.

If anyone has any suggestions of a better way to do such a structure in SQLite (Projects with entries) it would be greatly appreciated.

Show Accepted Answer

Guest Quick Reply (No URL, BBcode or HTML)

Last post by dena49
3 hours ago
Last post by herzog.morton
2 hours ago
Last post by kiera68
1 hour ago
Last post by reymundo.kertzmann
4 hours ago
Last post by davon16
1 hour ago
Last post by virgil.stamm
4 hours ago
Last post by ben27
4 hours ago
Last post by herzog.cheyanne
16 minutes ago
Last post by ettie.hayes
3 hours ago
Last post by brad.rohan
3 hours ago
Last post by phoebe92
35 minutes ago