ruby on rails - Access control and security: Should I have 1 massive ARTICLES table? -



ruby on rails - Access control and security: Should I have 1 massive ARTICLES table? -

if making scheme users can write articles cannot seen nor accessed other users, have single articles table permissions controls?

i not sure having single table content in security. yet, don't think want create new table containing articles each user.

is there improve way model this?

i don't believe appropriate create database responsible sort of authorization check. "users" database should aware of applications allowed access it. business rules governing authenticating users , determining users authorized access belong within application(s).

instead existing authorization tools managing access models. example: https://github.com/ryanb/cancan

ruby-on-rails security database-design

Comments

Popular posts from this blog

delphi - blogger via idHTTP : error 400 bad request -

c++ - compiler errors when initializing EXPECT_CALL with function which has program_options::variables_map as parameter -

How do I check if an insert was successful with MySQLdb in Python? -