Multiple Tables or Multiple Schema
Posted
by Yan Cheng CHEOK
on Stack Overflow
See other posts from Stack Overflow
or by Yan Cheng CHEOK
Published on 2010-03-26T02:55:57Z
Indexed on
2010/03/26
3:03 UTC
Read the original article
Hit count: 365
postgresql
|database-design
I am new in schema concept for PostgreSQL.
For the above mentioned scenario, I was wondering
- Why don't we use a single database (with default schema named public)
- Why don't we have a single table, to store multiple users row?
- Other tables which hold users related information, with foreign key point to the user table.
Can anyone provide me a real case scenario, which single database, multiple schema will be extremely useful, and can't solve by conventional single database, single schema.
© Stack Overflow or respective owner