I just noticed PostgreSQL's schemas for my first time.
(http://www.postgresql.org/docs/current/static/ddl-schemas.html)
I Googled around, but couldn't find any articles describing WHY or
WHEN to use schemas in database design.
Since the manual says HOW, could anyone here who has used schemas tak
I am in the middle of a project to convert non-schema databases to a
schema-based system. The main reason I am doing it is because I need to
do a join on tables between databases, which can only be done with an
contrib module which does not have all the "features" one might want
(such as use of in
iche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Im Auftrag von
> Miles Keaton
> Gesendet: Donnerstag, 25. November 2004 06:13
> An: [EMAIL PROTECTED]
> Betreff: [GENERAL] why use SCHEMA? any real-world examples?
>
> I just noticed PostgreSQL's schema
Miles Keaton wrote:
Since the manual says HOW, could anyone here who has used schemas take
a minute to describe to a newbie like me why you did? What benefits
did they offer you? Any drawbacks?
Well - it's a namespace feature, so at its simplest it lets you have two
objects with the same name.
o:[EMAIL PROTECTED]
Sent: Wed 11/24/2004 9:12 PM
To: [EMAIL PROTECTED]
Cc:
Subject: [GENERAL] why use SCHEMA? any real-world examples?
I just noticed PostgreSQL's schemas for my first time.
(http://www.postgresql.org/docs/current/static/ddl-schemas.html)
I Googled around, b
Hi,
Citing Miles Keaton <[EMAIL PROTECTED]>:
> I just noticed PostgreSQL's schemas for my first time.
> (http://www.postgresql.org/docs/current/static/ddl-schemas.html)
>
> I Googled around, but couldn't find any articles describing WHY or
> WHEN to use schemas in database design.
When your dat
> > Since the manual says HOW, could anyone here who has used schemas take
> > a minute to describe to a newbie like me why you did? What benefits
> > did they offer you? Any drawbacks?
I suspect the consumer of this feature for whom it would make the biggest
difference would be shrinkwrapped
