Hacker News new | ask | show | jobs
by mercurial 4282 days ago
That'd make in a very simple case (an app with a user_profile table) one view per user? This doesn't sound particularly appealing...
1 comments

"one view per user" - you can have a single VIEW, that filters rows based on user name ("owner_user_name" column in the base table). Or use some kind of mapping table for "user_name" <-> "table PK id". It gets more complicated with inherited user roles, but still manageable.