![]() Since there are hundreds of Pokémon, I gave them all the default form Pokémon id ( where p.is_default = 1) and then manually went through and updated the Pokémon ids for the entries for alternate forms. This SQL query below is what I used to add the new column. That way there is a way to see which Pokémon specifically the entry is for, rather than just the species id. To help combat this, I added a new column into the pokemon_v2_pokemonspeciesflavortext table called pokemon_id, which is a foreign key tied to the id in the pokemon_v2_pokemon table. Hence when trying to retrieve the Pokédex entries for, say, Alolan Raichu, you will get back all of the entries for both Kantonian Raichu and Alolan Raichu, with no way to differentiate which entry is for which form. While they all have their own unique Pokémon ids, they all share the same Pokémon species id. The issue arises for Pokémon species who have multiple different forms (i.e. Instead, the entries are tied to a Pokémon species. With the updates from Let's Go and Sword/Shield, I found that trying to fetch the different Pokédex entry descriptions, or "flavor text" were missing some important information for tying the entry to its associated Pokémon. Now you can write your SQL queries! Click on the "Play" icon to run them. To make a query, click on the "Open SQL Editor" button. You can explore the tables by clicking on the drop down arrows for the database you just opened in SQLiteStudio. This will just be the name that it's under in the SQLiteStudio sidebar. Optionally give the database a "name" input.Navigate to the db.sqlite3 file that you're using for your server. ![]() For the "File" input, click on the folder icon to browse your computer for an existing database file. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |