Related to issue #4 #6
Draft a database design, with most tables roughly described, that can contain all the needed info relating to Pokemon along with their data variation for each generation. The database must also allow marking certain Pokemon as caught (Only in the latest generation) and provide extensible functionality for asset paths (e.g. a Pokemon Sprites Table).
While designing, keep in mind the principles of database normalization to reduce the possibility of anomalies (Update, Insertion and Deletion) and repetition of information.
Related to issue #4 #6 Draft a database design, with most tables roughly described, that can contain all the needed info relating to Pokemon along with their data variation for each generation. The database must also allow marking certain Pokemon as caught (Only in the latest generation) and provide extensible functionality for asset paths (e.g. a Pokemon Sprites Table).
While designing, keep in mind the principles of database normalization to reduce the possibility of anomalies (Update, Insertion and Deletion) and repetition of information.