RE: first cut at a database table layout

["Creager, Robert S" <CreagRS@LOUISVILLE.STORTEK.COM>]

Hey Chris,

A couple of first pass questions.  These are rooted in the fact that you
have more dB experience than me, and I want to learn why you do things the
way you do.

1.  Why are you storing the observations in mas, rather than just plain
degrees?  Saving space (6 bytes per record)?
2.  I'm curious as to why to broke the observations table input bands, but
not the catalog_full table.  I happened to do just the opposite.
Originally, I had split for my trigger, but soon realized I didn't need to.
3.  What date range does abstime have?  I couldn't find it in the docs.  I'm
just wondering if it suffers from the 2038(?) thing, as you mention in table
observe comments it's seconds offset since 1970.
4.  On your views.  Aren't views a run time thing, in that if you look at
that table in successive queries (within a script for instance), multiple
queries are generated to 'fill' the view?  If so, why not have those select
into tables, rather than views?  I have not used views before.

Thanks,
Rob

> -----Original Message-----
> From: Chris Albertson [mailto:chrisalbertson90278@yahoo.com]
> Sent: Friday, February 08, 2002 11:29 AM
> To: TASS
> Subject: first cut at a database table layout
> 
> 
> 
> Here is a first cut at a database table layout.
> 
> http://albertson.sytes.net/~chris/TASS/CreateTables.sql
> 
> Don't worry if you're not an SQL expert.  It is
> just a list of column heading with data types.