Designing our user schema

Let's start with one of the most important introductory steps for adding a new table and schema into our application—designing the database table. This isn't just about designing the table, because you don't want to just think about the database impacts of creating/adding a new table and shaping the data model for this table; you also want to give a lot of thought to how the data model will impact your application's design and structure over time.

We'll start by figuring out what questions our application is trying to answer in regards to our new users schema. First off, we ask WHAT information we want to store:

Users------* id- username- email- encrypted_password- active-* inserted_at-* updated_at(* means it is ...

Get Phoenix Web Development now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.