Re: [GENERAL] Understanding Schema's

2010-12-23 Thread Jasen Betts
On 2010-12-15, Craig Ringer wrote: > On 12/15/2010 08:08 AM, Carlos Mennens wrote: >> I've recently switched from MySQL& have read the documentation for >> 'schema's' however I guess I'm just not at that level or really daft >> when it comes to database design. > > In terms of the way they work a

Re: [GENERAL] Understanding Schema's

2010-12-23 Thread Jasen Betts
On 2010-12-15, Carlos Mennens wrote: > On Tue, Dec 14, 2010 at 7:17 PM, Joshua D. Drake > wrote: >> You can cross query a schema but not a database. >> >> So you can create: >> >> create table fire.foo() >> create table ice.foo() >> >> And they are isolated from each other physically and logical

Re: [GENERAL] Understanding Schema's

2010-12-15 Thread Jacqui Caren-home
On 15/12/2010 00:20, Carlos Mennens wrote: Why would anyone in a random scenario want to have independent schema's to cross query? I'm just trying to see how this would be useful in any scenario. One very real example :-) When migrating from say mysql to PgSQL it is possible to populate a "myg

Re: [GENERAL] Understanding Schema's

2010-12-14 Thread Alban Hertroys
On 15 Dec 2010, at 3:14, Craig Ringer wrote: > It'd be nice if PostgreSQL offered more convenient ways to set an initial > schema for new connections, because for some use cases it'd be quite handy to > use a single database with many schema. Unfortunately most tools only know > how to ask for

Re: [GENERAL] Understanding Schema's

2010-12-14 Thread Craig Ringer
On 12/15/2010 08:08 AM, Carlos Mennens wrote: I've recently switched from MySQL& have read the documentation for 'schema's' however I guess I'm just not at that level or really daft when it comes to database design. In terms of the way they work and their operation, PostgreSQL "schemas" are i

Re: [GENERAL] Understanding Schema's

2010-12-14 Thread Bill Moran
On Tue, 14 Dec 2010 19:20:37 -0500 Carlos Mennens wrote: > On Tue, Dec 14, 2010 at 7:17 PM, Joshua D. Drake > wrote: > > You can cross query a schema but not a database. > > > > So you can create: > > > > create table fire.foo() > > create table ice.foo() > > > > And they are isolated from each

Re: [GENERAL] Understanding Schema's

2010-12-14 Thread Carlos Mennens
On Tue, Dec 14, 2010 at 7:17 PM, Joshua D. Drake wrote: > You can cross query a schema but not a database. > > So you can create: > > create table fire.foo() > create table ice.foo() > > And they are isolated from each other physically and logically but you > can query them both: > > SELECT fire.*

Re: [GENERAL] Understanding Schema's

2010-12-14 Thread Joshua D. Drake
On Tue, 2010-12-14 at 19:08 -0500, Carlos Mennens wrote: > I've recently switched from MySQL & have read the documentation for > 'schema's' however I guess I'm just not at that level or really daft > when it comes to database design. > > http://www.postgresql.org/docs/current/static/ddl-schemas.ht

[GENERAL] Understanding Schema's

2010-12-14 Thread Carlos Mennens
I've recently switched from MySQL & have read the documentation for 'schema's' however I guess I'm just not at that level or really daft when it comes to database design. http://www.postgresql.org/docs/current/static/ddl-schemas.html I'm trying to understand the relation between actual databases