mirror of
https://github.com/veekun/pokedex.git
synced 2024-08-20 18:16:34 +00:00
Merge branch 'generated-order'
This commit is contained in:
commit
13e2709668
4 changed files with 1440 additions and 1380 deletions
55
scripts/set_pokemon_order_columns.sql
Normal file
55
scripts/set_pokemon_order_columns.sql
Normal file
|
@ -0,0 +1,55 @@
|
|||
/*
|
||||
Pokémon species order: National dex order, except that families are grouped
|
||||
together around whichever member has the lowest National ID, with babies first.
|
||||
|
||||
Technically, the idea is to sort each evolutionary tree topologically, but
|
||||
National ID with babies first does the right thing. The id column happens to
|
||||
match Nat'l order, and the evolutionary chain IDs are in the right order too.
|
||||
*/
|
||||
|
||||
UPDATE pokemon_species ps
|
||||
SET "order" = ps_order."order"
|
||||
FROM (
|
||||
SELECT ps_sub.id, ROW_NUMBER() OVER (ORDER BY ps_sub.evolution_chain_id,
|
||||
ps_sub.is_baby DESC, ps_sub.id) "order"
|
||||
FROM pokemon_species ps_sub
|
||||
) ps_order
|
||||
WHERE ps.id = ps_order.id;
|
||||
|
||||
|
||||
/*
|
||||
Pokémon form order: Same as species order, with a species' forms ordered as
|
||||
specified by pokemon_forms.form_order. Since form_order can have duplicate
|
||||
orders to indicate that they should fall back on ordering by name, so can
|
||||
pokemon_forms.order.
|
||||
*/
|
||||
|
||||
UPDATE pokemon_forms pf
|
||||
SET "order" = pf_order."order"
|
||||
FROM (
|
||||
SELECT pf_sub.id, DENSE_RANK() OVER (ORDER BY ps."order",
|
||||
pf_sub.form_order) "order"
|
||||
FROM pokemon_forms pf_sub
|
||||
JOIN pokemon p ON pf_sub.pokemon_id = p.id
|
||||
JOIN pokemon_species ps ON p.species_id = ps.id
|
||||
) pf_order
|
||||
WHERE pf.id = pf_order.id;
|
||||
|
||||
|
||||
/*
|
||||
[Functional] Pokémon order: Same as form order, except not all forms have their
|
||||
own functional Pokémon, so we need to close the gaps.
|
||||
|
||||
These aren't supposed to have duplicate orders, but this query will give them
|
||||
duplicate orders where applicable anyway so that the unique constraint can
|
||||
complain if needed instead of the query silently ordering things arbitrarily.
|
||||
*/
|
||||
|
||||
UPDATE pokemon p
|
||||
SET "order" = p_order."order"
|
||||
FROM (
|
||||
SELECT p_sub.id, DENSE_RANK() OVER (ORDER BY pf."order") "order"
|
||||
FROM pokemon p_sub
|
||||
JOIN pokemon_forms pf ON p_sub.id = pf.pokemon_id AND pf.is_default = True
|
||||
) p_order
|
||||
WHERE p.id = p_order.id;
|
Loading…
Add table
Add a link
Reference in a new issue