[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Calculation of mag errors
- To: TASS <tass@listserv.wwa.com>
- Subject: Re: Calculation of mag errors
- From: Chris Albertson <chrisalbertson90278@yahoo.com>
- Date: Thu, 03 Mar 2005 15:57:56 -0800 (PST)
- Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
- DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;b=QKqc0JzlJrKSyLTQe/knnksUKJ+bag+akGuJKtwOQYVEoac7ySGwPLIyhCPIKHJ6RgJLuTN1UiSRK64h+OARVrafo20YVFyMnYkqg0zIO2c1oDBikCuzHANE/nB158wxatkMSrQweXcnaeo61XCkzsD4dpEp56k9LlI3LQUoUKs= ;
- Sender: owner-tass@listserv.wwa.com
--- Stupendous Man <richmond@stupendous.cis.rit.edu> wrote:
> In other words, we _could_, if desired, leave the
> Mark IV database as it is, not changing any values in
> the stored records, but add a bit of code to the
> access scripts so that they use a table value for the
> quoted uncertainty instead of the value stored in the database.
With an SQL database you could do the above by redefining the
table as a "view" Users (including any scripts) would not
notice the change. It would be hidden inside the database.
The "view" redefines the tabe to be a join of two tables.
The view could also redefine the table such that the errors
are polynominal functions of the magntude. Either way the
change would be transparent to users. Scripts, web pages
and what have you wuld not need to be changed.
=====
Chris Albertson
Home: 310-376-1029 chrisalbertson90278@yahoo.com
Cell: 310-990-7550
Office: 310-336-5189 Christopher.J.Albertson@aero.org
KG6OMK
__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/