Hi! It's really just a convenience-thing to organize your data in a more intuitive way. We're running several online magazines, each of those with a sort of "entity-database", but each with their own articles. So we've just put the entity-data in the public schema, whereas the magazine-specific data is going in their own schemata. That way we can simply use the very same queries for all of our magazines' applications, just by implementing the magazine-schema as a variable which is set at query-runtime.
Kind regards Markus > -----Ursprüngliche 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 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 take > a minute to describe to a newbie like me why you did? What benefits > did they offer you? Any drawbacks? > > Thanks for your time. > > - Miles > > ---------------------------(end of > broadcast)--------------------------- > TIP 8: explain analyze is your friend > ---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
