Re: Units of Measurement in the Database Model

From: Randall S. Becker <r>
Date: Fri, 12 Apr 2002 22:42:14 GMT
Message-ID: <apJt8.4467$OI1.2324_at_news02.bloor.is.net.cable.rogers.com>


"--CELKO--" <71062.1056_at_compuserve.com> wrote in message news:c0d87ec0.0204120758.3f621ef5_at_posting.google.com...
> >> How should the database be organized in regards to measurements
> recorded, and the units of measurement (UOM) used to record them? <<
>
> I devoted a chapter to scales and measurements in my book DATA &
> DATABASES; it might help.
>
> I like to have one and only one UOM for a column inside the database,
> and then use VIEWs to display it in "customary units" for humans who
> all seem to have different customs. So the database is in kilograms
> and the screen is in pounds & ounces, but the American don't know
> this. The exception is when the UOM has a well-understood name, such
> as the 'A' series paper sizes, that does not translate well. Quick,
> in your head do the math and tell me how big is an A4 sheet in inches!
> Arrrgh!

Speaking as a very old DBA, I'm with CELKO on this one. I want one and only one UOM (Kg or Lbs; ft or m; etc), preferably in a commonly compatible system (SI units are good for this) and use VIEWs to convert. Some DBMS systems support protection views that can back convert for INSERT operations. VIEWs can get named based on the relevant UOM if you want. Received on Sat Apr 13 2002 - 00:42:14 CEST

Original text of this message