0

In my fantasies, it looks something like this:

User 1:

SHOW TABLES;
+-----------------------+
| Tables_in_my_database |
+-----------------------+
| table_1               |
| table_2               |
+-----------------------+

SELECT * FROM table_1;
+----+---------+---------------------+
| id | name    | created_at          |
+----+---------+---------------------+
| 1  | Erik    | 2014-09-09 18:31:34 |
| 2  | Richard | 2014-09-09 18:31:34 |
+----+---------+---------------------+

User 2:

SHOW TABLES;
+-----------------------+
| Tables_in_my_database |
+-----------------------+
| table_1               |
| table_2               |
| table_3               |
+-----------------------+

SELECT * FROM table_1;
+----+---------+---------------------+---------------------+
| id | name    | created_at          | email               |
+----+---------+---------------------+---------------------+
| 1  | Erik    | 2014-09-09 18:31:34 | [email protected]    |
| 2  | Richard | 2014-09-09 18:31:34 | [email protected] |
+----+---------+---------------------+---------------------+

Can we something like this be build in any database system?

1
  • 1
    Most DBMS has VIEW
    – Serg
    Commented May 18, 2016 at 9:40

1 Answer 1

0

Do you define "different content" as row filtering via security settings? That is pretty standard - and pretty unusual (as in: standard for high security, not all databases support this thinking)... SQL Server for example is just adding this with version 2016 due this year. In most cases... people do not bother as the filtering of what data is visible is done on the application layer (possibly in a server obviously).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.