---
# System prepended metadata

title: '`pg` and Router Feature Set'

---

# `pg` and Router Feature Set

## `pg` section

### Feature: Getting all the Pokémon from the database
**Dev Story**: Software Engineer Riley wants to be able to get data on all the Pokémon we have in the database

Write a query that gets all the Pokémon

### Feature: Getting a single Pokémon from the database
** Dev Story**: Software Engineer Tom wants to be able to get data on any single Pokémon from the database

Write a query that gets a single Pokémon

### Feature: All Pokémon Route

**Dev Story**: Instead of putting all the queries inside a function, Lead Engineer Gianni wants to separate out the different types of queries/feature data into their own Express routes

**User Story**: When Jess goes to our website, she can go to localhost:1330/ to get a list of all the Pokémon

Write a route that uses the all Pokémon query

### Feature: Single Pokémon Route

Write a route that uses the single Pokémon query

**User Story**: When LB goes to our website, they can go to localhost:1330/2 to get the second Pokémon

## Router Section

### Feature: Creating a Pokémon

**User Story**: When Jason goes to our website, they can go to our site to view a form to create a Pokémon

**Express Route**

Write a route that handles a POST request

**SQL Query**

Inside the route, write a query that gets the data from the client (the website form or an API testing tool) and creates an entry in the database