RE: Data Processing Switch

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

Hey Chris,

Well, I based it on your previous work, but have a lot of referential
integrity links and other stuff added on top.  So the table schema will look
similar to what you've done, but then I use lots of Perl (DBI) and SQL to
manage the rest.

I import nearly the entire Tycho2 db, and then trim it down into another
table using Arne's color transformations and Michael's selection criteria.
This is how I drive matching reduced star lists to reality (using MATCH ala
Michael R), and also how I generate color information.

I'm storing the color terms for a nights observations, and zero points on a
frame basis within the dB, but have not yet setup the trigger which will
propagate that change through the dB.  So I just run an UPDATE when I change
any of those values for now.

I've set up the tables so that, for instance, if I decide I want to remove
an image from the data (clouds or something), I can delete an entry from a
table, and that will cascade through the dB and end up adjusting the catalog
table to remove the influence the stars in that file had on the catalog
information (composite ra, dec, magnitudes for each band).  Similarly, when
I update an observation with a star id and magnitude (calibrated, not
instrumental), the dB will handle adding that information to an existing
catalog star (or creating a new one if appropriate).  I'm using a PostgreSQL
trigger for this.

I'd be happy to post the schema, and supporting scripts if there is any
interest.  It's not done yet, but getting there.

Cheers,
Rob

> -----Original Message-----
> From: Chris Albertson [mailto:chrisalbertson90278@yahoo.com] 
> Sent: June 02, 2003 4:40 PM
> 
> What are you doing re. a database?  I was about to start a db
> project myself.   
>