- To: <slug-chat@xxxxxxxxxxx>
- Subject: Re: [chat] Postgres
- From: Peter Faulks <peter@xxxxxxxxxxxxxxx>
- Date: Wed Sep 12 13:29:02 2001
- Reply-to: pfaulks@xxxxxxxxxx
On Wed, 12 Sep 2001 10:58, Ben Leslie wrote:
> > I'm finally getting around to looking at Postgres, and I have to say I
> > _dont_ like the idea of the global object id. This implies a connection
> > between different databases which IMO simply should not exist.
>
> They are internal structures. It is really irrelevant from a design point
> of view. You use it like you would any other database by creating id fields
> in each record for creating relations.
Agreed of course you still need your own primary/foreign key setup. What I
dislike about the global id is it means that a database has to be 'built'
where it is being hosted, ie you cannot move a database by simply copying the
files.
My experience with databases is limited to single user desktop applications
(Where I found Sybase SQL Anywhere ideal), and I guess it is a paradigm shift
into the world of database 'farms', but I still feel that if you want a link
between different databases, it should be a feature designed into the
database structures, not build into the database engine.
Consider a web co-hosting scenerio, your database has nothing to do with the
other dozens or hundreds of databases managed on a host. And nor should it.
Regards