Active Record and Associations with Sinatra
Sinatra is a domain specific language that wraps HTTP requests and responses on top of Rack. Sinatra is similar to Ruby; they are both web frameworks. Sinatra is used for smaller web applications.
When you want to build something, like say a web application where a user can submit a blog post, ActiveRecord is a great framework to use to keep track of databases and their data, and also their associations.
Here is a sample migration for creating the posts table. author_id is the association of the posts to the author.
1 2 3 4 5 6 7 8 9
Eventually you will have a database that will look something like these charts, filled with seed data.
Post_tags table —> needed because posts has many tags, and tags has many posts, so there must be a join table created to satisfy those requirements. It is not simply just a table that either has_many or belongs_to anymore.
So here, the first blog post called “cats” will have the tags cats. But for the second blog post called “dogs” it will have the tags dogs, and also parks.
Now here are the models
1 2 3 4 5
because the posts table has “author_id”, which means that posts belongs to an author, and an author will have many posts. Also, you must write “has_many” “:post_tags” so you can mention the join table before mentioning that posts “has_many” tags through the join table.
1 2 3
1 2 3
1 2 3 4
1 2 3 4
When writing belongs_to for a class, whatever it belongs to will typically have “has_many”.
eg. class Author “has_many” posts, while Posts “belong_to” Author
When associating with join tables, mention the join table, and then write “has_many” something through the join table in the next line. eg. Like so in “class Posts” above.
Provided that you have seed data, and that you want to associate a post with an author, you can first think about the author as the parent, and posts as the child (because posts belongs to an author, and an author has many posts.)
1 2 3 4 5 6
When associating with Sinatra, if the model of is associated with another model, you can write that association inside the Controller. If there was a blog controller with Sinatra:
1 2 3 4 5 6 7 8 9 10 11
In the blogs controller, if you wanted to create a new blog post and went to the form to input the new blog post data, you can also asisgn it to an author, to have an author association too. As long as you associated with authors in the post model, you can access it.