Received: from bender.toppoint.de (bender.toppoint.de [195.244.243.2]) by hub.org (8.9.3/8.9.3) with ESMTP id WAA02445; Thu, 3 Feb 2000 22:07:31 -0500 (EST) (envelope-from marten@feki.toppoint.de) Received: (from uucp@localhost) by bender.toppoint.de (8.9.3/8.9.3) id EAA01920; Fri, 4 Feb 2000 04:04:04 +0100 (MET) >Received: (from marten@localhost) by feki.toppoint.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id WAA04803; Thu, 3 Feb 2000 22:19:06 +0100 From: Marten Feldtmann Message-Id: <200002032119.WAA04803@feki.toppoint.de> Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL In-Reply-To: <26715.949561209@sss.pgh.pa.us> from Tom Lane at "Feb 3, 2000 02:00:09 am" To: Tom Lane Date: Thu, 3 Feb 2000 22:19:06 +0100 (CET) CC: chris@bitmead.com, pgsql-hackers@postgreSQL.org, pgsql-sql@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL60 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII > Chris Bitmead writes: > > I'll comment on the other issues later ... but I will say that I don't > think it's acceptable to add *any* overhead to standard-SQL queries > in order to support inheritance better. The vast majority of our users > want SQL performance and don't give a damn about inheritance. We have > to pay attention to that. > Well said ! Actually I'm a little bit uncertain what ORDBMS really improves ? After writing a full mapper and wrapper for PostgreSQL and a Smalltalk dialect I see really no usage for these additional inheritance features databases like PostgreSQL offer. Some points about this: - all these additional features are very specific to PostgreSQL and are not compatible with other databases. Writing an application based on these features results in non-portable systems. - Speed is still a very, very important feature for a database. A single query, which uses about 5 seconds because the optimizer is not very clever to use several indices to improove the query execution is much more worse and can change the structure of the whole application program. - when creating automatic sql-queries through a mapper one can get very complicated sql queries which tests the parser very hard and the limits of PostgreSQL has been seen very quickly during the development of the wrapper above. What I'm missing from these new database are structural changes to the query system: the possibility to execute complicated concatenated queries on the server .. perhaps with different parameters. Just some ideas about all these nice features Marten