Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have experienced a situation where "current_user" needs be tightly connected to a model, but I handled it all in the Controller and it works pretty well. Here are some examples:</p> <p>My model is "Photos". Photos are owned by users, and how people interact with photos is obviously tightly related to whether or not they own the photo.</p> <p>In the show action I need to load either the existing rating a user has given to a photo (so they can edit it) or allow them to create a new one:</p> <pre><code>def show @photo = Photo.find(params[:id]) if user_signed_in? if @rating = current_user.ratings.find_by_photo_id(params[:id]) @rating @current_user_rating = @rating.value else @rating = current_user.ratings.new @current_user_rating = "n/a" end end end </code></pre> <p>When people create photos I want them to be automatically assigned to the current user.</p> <pre><code>def new @photo = Photo.new end def create @photo = current_user.photos.create(params[:photo]) if @photo.save redirect_to user_path(current_user), :notice =&gt; t('photo.notice.created') else render 'new' end end </code></pre> <p>Only the owners of a photo can change them:</p> <pre><code>def edit @photo = Photo.find(params[:id]) if @photo.user == current_user render 'edit' else redirect_to user_path(current_user), :alert =&gt; t('application.error.unauthorized') end end def update @photo = current_user.photos.find_by_id(params[:id]) @photo.update_attributes(params[:photo]) if @photo.save redirect_to user_path(current_user), :notice =&gt; t('photo.notice.updated') else render 'edit' end end </code></pre> <p>This approach is based on the constraints that a "current_user" object is tied to the session, which only the controller knows about. So, in short, I have yet to find a good way to integrate "current_user" into a model, but I've been able to find (I think) pretty clean ways to tie the model and controller together so that this can be provided by the controller.</p> <p>One fairly simple solution to most problems, if your controller is starting to get messy, would be to take a chunk of logic and define as a method in the model, but require one argument = a user object. Then you can just feed "current_user" to that method from your controller and the model handles the rest.</p> <p>Good luck! Also, if anyone else has any better ideas for this, I'd love to hear them!</p>
    singulars
    1. This table or related slice is empty.
    1. POWhere to put business logic that requires the current_user to be known? (Rails)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAndrew
    1. USAndrew
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhere to put business logic that requires the current_user to be known? (Rails)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks for your answer, appreciate it. Your code will likely work, but it does seem kind of wrong to put that in the controller (my opinion only). I'm thinking of putting ALL of my business logic into a single module/class and then mix it in with the models that need it. This way, I know all the logic is in one place (great), and I don't clutter the model or the controller much. What are your thoughts on this?
      singulars
      1. PO
      1. USZabba
    2. COThere's no reason *not* to group all your logic in one place. As long as you're happy with the outcome, the code works as expected, and it keeps you from wondering "where is that particular bit of code again?", then you're in good shape. However... (see next comment due to character limits)
      singulars
      1. PO
      1. USAndrew
    3. COThe more I've worked with Rails the more I've gotten comfortable with the kind of "flow" that exists in the MVC pattern for web apps. For me, I expect most logic to relate to the data in the database, and so it belongs in the model. The logic that handles sessions and HTTP requests to get stuff out of the models feels right in the controller, and a bit of presentation logic makes sense in the view. The trick is, in these edge cases, things like "current_user" seem like data, but really it's not, it's totally related to the HTTP request. (next comment)
      singulars
      1. PO
      1. USAndrew
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload