Storing value in session vs in DB - Rails

Question

I am building a team management app in Rails where :users has many :organizations. I would like for users to be able to switch between organisations and manage them individually without having the /organizations/:id/ in the URL. Due to Wildcard SSL certificate costs, I would also like to avoid using subdomains to identify the organization.

As I understand it, this leaves two options:

Store the current organization in the DB.
Store the current organization in the session.

What would be the best option here?

Thanks

If you're just not wanting the id in the URL, you can use something like FriendlyId to create slugs for each organization, which can be as random as you'd like. — XML Slayer
– XML Slayer, Commented Feb 27, 2017 at 3:25

Michael Chaney · Accepted Answer · 2017-02-27 03:21:27Z

2

Simply store it in the session, there's no reason to do it any other way. I would also create a before_action in the application controller to automatically load the organization into an instance variable available to your controllers and views.

answered Feb 27, 2017 at 3:21

Michael Chaney

3,04922 silver badges27 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Storing value in session vs in DB - Rails

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related