From: Emmanuel Charpentier <charpent@bacbuc.dyndns.org>
To: pgsql-interfaces@postgresql.org
Subject: Re: PgAdmin problem
Date: Fri, 21 Feb 2003 20:33:22 +0100
Message-ID: <b35uu2$1cre$1@news.hub.org> (raw)
In-Reply-To: <00A42578900AD411BCFD00A0C978DC9304DC020D@mail.coba.usf.edu>
References: <00A42578900AD411BCFD00A0C978DC9304DC020D@mail.coba.usf.edu>
Agrawal, Manish wrote:
> 2. On another note, is there a tool like the MS Access front end that lets
> you create constraints graphically by simply dragging and dropping columns
> between tables and views by simply dragging columns from the respective
> tables into the design window.
You might be pleased wit OpenOffice : The 643 version, with the newer
("snapshot") ODBC drivers by Hiroshi Inoue is quite efficient at emulating
the "query" interface of MS-Access.
But keep in mind that MS-Access (and OO's) abilities are limited in this
respect. For one thing, they won't accept subselects as column sources. If
you need that, you have to define a view, and use it as a column source, or
define your query/view in server-side SQL (you may fool around with cut and
paste and many "query definition" windows.
One thing that you won't be able to do with OOo is to define
crosstabulation queries/views. Fortunately, the spreadsheet allows you to
define "data pilot" zones that give you "almost the same" functionality, as
far as you don't need crosstab *views*.
I think that in 7.3, one may define a function writind dynamycally a big
"left outer join" query and returning the corresponding set of rows, which
would be a tad closer. But what's the point ?
> 3. Also, updatable views would make Postgresql so much easier to use.
You may do that, but yu'll have to define the update function by yourself.
The reason is that determining what should be the "update" rule is
intrinsically *hard* in the general case. See "The rule system" chapter and
following in the Postgres server programming manual.
The limited abilities of MS-Acces views (no subselects, for example) makes
easier the building of a "reasonable" update rule. No such luck in Postgres !
> The reason I ask is that if that were the case, PostgreSQL would be
> enormously popular beyond expectations. At the very least, introductory
> database courses in business schools could so easily use PostgreSQL instead
> of MS Access.
<Rant>
Huh ?
The only reasonable database systems course in a buisness school should be
given with a M-16 ... ;-] More seriously : any "manager" I've seen trying
to tackle a database problem ended up with his/her head so up his/her a*se
that one had to call for a *thoracic* surgeon.
Every time.
The reason seems to be that they seem to be allergic to Codd's algebra (or
any kind of algebra past elementary linear algebra used in accounting and
elementary calculus). Even physicians, of all types, seem more suited to
database design and use ...
</Rant>
Hope this helps,
Emmanuel Charpentier
--
Emmanuel Charpentier
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 using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: charpent@bacbuc.dyndns.org
Subject: Re: PgAdmin problem
In-Reply-To: <b35uu2$1cre$1@news.hub.org>
* 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