From: sad <sad@bankir.ru>
To: Iain <iain@mst.co.jp>
To: josh@agliodbs.com
To: Karsten Hilbert <Karsten.Hilbert@gmx.net>
To: pgsql-sql@postgresql.org
Subject: Re: surrogate key or not?
Date: Mon, 26 Jul 2004 15:13:37 +0400
Message-ID: <200407261513.38001.sad@bankir.ru> (raw)
In-Reply-To: <002801c472fc$be62af40$7201a8c0@mst1x5r347kymb>
References: <1090325769.3241.27.camel@dicaprio.akademie1.de>
<200407231020.59843.josh@agliodbs.com>
<002801c472fc$be62af40$7201a8c0@mst1x5r347kymb>
hello
> This reminds me of a project I worked on many years ago, I was pretty much
> fresh out of university writing a system for a large medical practice -
> itwas principally for accounting purposes. I made lots of suggestions like
> Josh's, only to get replies like Karsten's. I the progammer wanted to
> codify everything so as to enable data analysis (ie linking complaints and
> diagnosis, etc) but the doctors wern't interested. They just wanted to
> write free text comments. And the reason for it (as far as I can tell) is
> the distinction between general practice and reseach (such as
> epidemiology). So (GPs) are not so much searching for new knowlege in their
> patients records, as applying the knowlege gained from research (done by
> researchers) to treat individual patients.
Here the situation quite similar, a customer dictate drives the practice far
far from logic.
EVERY database i had desined in few years have been turned into a container of
textual MEMOs completely unstructured. (because of patches and makeups)
USER DO NOT WANT TO TAKE CARE OF THEIR INPUT.
i do not know how are you all programming, really hope you are in defferent
circumstances. Here a customer itself is a user and itself is a [man who
formulate a problem] then every stupid idea to simplify input immediately
turns to an urgent official order to do.
Sorry. That is my work.
Thank you all again for very usefull discussion on Surrogate Keys.
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-sql@postgresql.org
Cc: sad@bankir.ru, iain@mst.co.jp, josh@agliodbs.com, Karsten.Hilbert@gmx.net
Subject: Re: surrogate key or not?
In-Reply-To: <200407261513.38001.sad@bankir.ru>
* 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