pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris <chris@bitmead.com>
To: Marten Feldtmann <marten@feki.toppoint.de>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-hackers@postgreSQL.org <pgsql-hackers@postgreSQL.org>
Cc: pgsql-sql@postgreSQL.org
Cc: pgsql-general@postgreSQL.org
Subject: Re: [SQL] Re: [HACKERS] Proposed Changes to PostgreSQL
Date: Sat, 05 Feb 2000 12:52:16 +1100
Message-ID: <389B8250.EB7CF08A@bitmead.com> (raw)
References: <200002041815.TAA07061@feki.toppoint.de>

Marten Feldtmann wrote:

>  Hmm, and yes one may find problems where the pure 
> relational system is 100x faster than your ODBMS.
> 
>  After doing a project with VERSANT and VisualWorks 
> (election projection system for the first television 
> sender here in Germany) I like the idea of OODBMS, 
> but I've also noticed, that they are  not the 
> solution to all problems.

Give me a clear application spec and VERSANT, and I will ALWAYS flog
Oracle into the dust. But...

Where SQL comes into it's own is _conveniently_ doing queries that I
never thought of when I first designed my app. Of course many ODBMSes
have SQL or similar too.

>  Joins per se are not that bad .. it depends on when 
> and how they are used and how good the analyzer of 
> the database is and how good he uses the indices to 
> get the job done.

Take the simple SUPPLIER, PART and SUPPLIER_PART situation. The very
fact that you've got an extra table here means you've got to touch many
more disk pages and transfer more data. An RDBMS just can't win when the
ODBMS data model is designed right.

>  One very good point is the query language of the 
> rdbms systems. On the odbms side no standard is 
> really available, which can be seen as the sql of 
> the odbms.

There is a standard called OQL which is very similar to SQL. It's just
rather poorly supported.

--
Chris Bitmead
mailto:chris@bitmead.com



view thread (68+ messages)  latest in thread

Message-ID: <389B8250.EB7CF08A@bitmead.com>
Permalink:  ../389B8250.EB7CF08A@bitmead.com/
Also on:    postgresql.org/message-id/389B8250.EB7CF08A@bitmead.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: chris@bitmead.com, marten@feki.toppoint.de, peter_e@gmx.net, pgsql-hackers@postgreSQL.org, pgsql-general@postgreSQL.org
  Subject: Re: [SQL] Re: [HACKERS] Proposed Changes to PostgreSQL
  In-Reply-To: <389B8250.EB7CF08A@bitmead.com>
  References: <200002041815.TAA07061@feki.toppoint.de> <389B8250.EB7CF08A@bitmead.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox