- Databases
- Relational Databases
- Query Builder - Knex
Build an API that persists data to SQLite3 or MySQL.
Use knex migrations to create the following database tables:
Users
- id: primary key, autoincrements.
- name: up to 128 characters long, required.
- createdAt: defaults to the current date and time.
Posts
- id: primary key, autoincrements.
- userId: references the id in the users table.
- text: not size limit, required.
- createdAt: defaults to the current date and time.
Tags
- id: primary key, autoincrements
- tag: string up to 16 characters long, unique.
- createdAt: defaults to the current date and time.
Establish a many to many relationship between Posts and Tags.
The same tag can be added to different posts and a post can have multiple tags.
Add any tables necessary to accomplish this.
Seed test data into your tables using knex.
Implement the following endpoints:
-
[POST]
/usersThis route should save a new user to the server. -
[GET]
/usersThis route will return an array of all users. -
[GET]
/users/:idThis route will return the user with the matchingid. -
[GET]
/users/:id/postsreturns all posts for the user with the specifiedid. -
[DELETE]
/users/:idThis route should delete the specified user. -
[POST]
/postsThis route should save a new post to the server. -
[GET]
/postsThis route will return an array of all posts. -
[GET]
/posts/:idThis route will return the post with the matchingid. -
[DELETE]
/posts/:idThis route should delete the specified post. -
[POST]
/tagsThis route should save a new tag to the server. -
[GET]
/tagsThis route will return an array of all tags -
[GET]
/tags/:idThis route will return the tag with the matchingid. -
[DELETE]
/tags/:idThis route should delete the specified tag.
- add a [GET]
/posts/:id/tagsendpoint that returns all tags for the post with the specifiedid. - have the post returned by the [GET]
/posts/:idendpoint include the user name(not the id) and the tags associated with the post.