IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Ignore:
Timestamp:
Sep 2, 2008, 9:37:06 AM (18 years ago)
Author:
eugene
Message:

substantial work on flatcorr; reworked the sequence somewhat

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/ippTools/share/pxadmin_create_tables.sql

    r19219 r19325  
    976976) ENGINE=innodb DEFAULT CHARSET=latin1;
    977977
    978 CREATE TABLE flatcorrExp (
     978-- XXX deprecate this table
     979-- CREATE TABLE flatcorrExp (
     980--         corr_id BIGINT,
     981--         chip_id BIGINT,
     982--         PRIMARY KEY(corr_id, chip_id),
     983--         FOREIGN KEY (corr_id)  REFERENCES  flatcorrRun(corr_id),
     984--         FOREIGN KEY (chip_id)  REFERENCES  chipRun(chip_id)
     985-- ) ENGINE=innodb DEFAULT CHARSET=latin1;
     986
     987-- these two tables link the flatcorrRun to the associated chip and camera runs
     988CREATE TABLE flatcorrChipLink (
    979989        corr_id BIGINT,
    980990        chip_id BIGINT,
     
    982992        FOREIGN KEY (corr_id)  REFERENCES  flatcorrRun(corr_id),
    983993        FOREIGN KEY (chip_id)  REFERENCES  chipRun(chip_id)
     994) ENGINE=innodb DEFAULT CHARSET=latin1;
     995
     996CREATE TABLE flatcorrCamLink (
     997        corr_id BIGINT,
     998        cam_id BIGINT,
     999        PRIMARY KEY(corr_id, cam_id),
     1000        FOREIGN KEY (corr_id)  REFERENCES  flatcorrRun(corr_id),
     1001        FOREIGN KEY (cam_id)  REFERENCES  camRun(cam_id)
    9841002) ENGINE=innodb DEFAULT CHARSET=latin1;
    9851003
Note: See TracChangeset for help on using the changeset viewer.