From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | sqllist <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: abstract data types? |
Date: | 2001-01-26 17:02:57 |
Message-ID: | 3A71ADC1.1D717C6F@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Mr. Reid,
> To answer your question, it is a bit hard to say at the moment as the
> design schema for our project has only just been started. The draft
> versions of the ISO standard that I have seen use an object oriented
> data model, so to me it makes sense to try and keep the database schema
> as close as possible to this (minimise data impedance).
>
> Briefly, at its' simplest the schema will probably use a two tier approach.
<snip>
Let me preface this by saying that I know squat-all about building
geometric databases. My background is in db's for accounting, billing,
scheduling, and fundraising.
Given that .., over the last 3 months, I have become a believer in C.J.
Date and Fabian Pascal, who point out quite a few ways that
object-oriented and relational approaches to data problems *cannot* be
made to reconcile. See http://www.firstsql.com/dbdebunk for some
examples of their objections.
Of course, Date and Pascal reject Object Oriented approaches entirely,
something I'm not ready to do ... but I do see that trying to build a
database accessable to both a range of OODB tools and relationally
compliant is not achievable.
-Josh Berkus
--
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh(at)agliodbs(dot)com
and data management solutions (415) 436-9166
for law firms, small businesses fax 436-0137
and non-profit organizations. pager 338-4078
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Kyle | 2001-01-26 17:05:27 | Re: Rule not invoked in 7.1 |
Previous Message | Jan Wieck | 2001-01-26 16:52:40 | Re: Rule not invoked in 7.1 |