Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As I know CanCan and declarative_authorization, and I implemented role-based authorizations with both, I recommend CanCan. Just my two cents. </p> <p><strong>Example</strong> (untested, unfortunately I cannot test here and I have no access to my code)</p> <p>So let's say we have a structure like this:</p> <pre><code>class User &lt; ActiveRecord::Base belongs_to :role end class Role &lt; ActiveRecord::Base has_many :users # attributes: project_read, project_create, project_update end </code></pre> <p>Then, CanCan could look like this:</p> <pre><code>class Ability include CanCan::Ability def initialize(user) @user = user @role = user.role # user can see a project if he has project_read =&gt; true in his role can :read, Project if role.project_read? # same, but with create can :create, Project if role.project_create? # can do everything with projects if he is an admin can :manage, Project if user.admin? end end </code></pre> <p>You can find all information you need in the CanCan wiki on github. Personal recommendation to read: </p> <ul> <li><a href="https://github.com/ryanb/cancan/wiki/Defining-Abilities" rel="nofollow">https://github.com/ryanb/cancan/wiki/Defining-Abilities</a></li> <li><a href="https://github.com/ryanb/cancan/wiki/Defining-Abilities-with-Blocks" rel="nofollow">https://github.com/ryanb/cancan/wiki/Defining-Abilities-with-Blocks</a></li> <li><a href="https://github.com/ryanb/cancan/wiki/Authorizing-Controller-Actions" rel="nofollow">https://github.com/ryanb/cancan/wiki/Authorizing-Controller-Actions</a></li> </ul> <p>Basically you just need to extend the example above to include your roles through your relations. To keep it simple, you can also create additional helper methods in <code>ability.rb</code>.</p> <p>The main mean caveat you may fall for (at least I do): Make sure your user <em>can</em> do something with a model before you define what the user <em>can't</em>. Otherwise you'll sit there frustrated and think "but why? I never wrote the user can't.". Yeah. But you also never explicitly wrote that he can... </p>
    singulars
    1. This table or related slice is empty.
    1. POAuthorization in Rails 3.1 : CanCan, CanTango, declarative_authorization?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USpduersteler
    1. USpduersteler
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAuthorization in Rails 3.1 : CanCan, CanTango, declarative_authorization?
      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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI have implemented cancan.. but can't figure out how to define/restrict user for a specific instance (of say project). Any e.g. would be really helpful. There is indirect connection between User and Project... 1. TeamMembers has many Users 2. Teams has many TeamMembers 3. Project has one Team
      singulars
      1. PO
      1. USRaj Lalwani
    2. COupdated with an example.
      singulars
      1. PO
      1. USpduersteler
    3. COdo I need to install cancan AND create a role model? I don't see in the cancan documentation that it is needed. Can you please explain this? thanks
      singulars
      1. PO
      1. USNick Ginanto
 

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