50 | | INSERT INTO sunum_queue ( |
51 | | SELECT NEXTVAL('sunum_queue_key'::regclass), lev1.sunum, 'aia.lev1' AS series_name, NOW() AS TIMESTAMP, lev1.recnum |
52 | | FROM aia.lev1 LEFT OUTER JOIN sunum_queue ON lev1.sunum = sunum_queue.sunum |
| 50 | SELECT nextval('sunum_queue_key'::regclass), lev1.sunum, 'aia.lev1 bulk' AS series_name, now() as timestamp, lev1.recnum |
| 51 | FROM vso.aia__lev1 LEFT OUTER JOIN sunum_queue ON lev1.sunum = sunum_queue.sunum |
59 | | Note that this should only be used after the other options. Due to the way that the JMD pulls records out of the queue table, more recent observations will take precidence. |
| 58 | Note that this query does not have 'prime key logic', and if used for times from 2010 could cause multiple images to be retrieved for each observation. If you have the VSO shadow tables built, you can do: |
| 59 | |
| 60 | {{{ |
| 61 | INSERT INTO sunum_queue ( |
| 62 | SELECT nextval('sunum_queue_key'::regclass), aia__lev1.sunum, 'aia.lev1 bulk' AS series_name, now() as timestamp, aia__lev1.recnum |
| 63 | FROM vso.aia__lev1 LEFT OUTER JOIN sunum_queue ON aia__lev1.sunum = sunum_queue.sunum |
| 64 | WHERE sunum_queue.sunum IS NULL and wave=304 and T_REC_INDEX IN ( |
| 65 | 1135814444,1135836044,1135857644,1135879244,1135900844,1135922444,1135944044 |
| 66 | ... |
| 67 | )); |
| 68 | }}} |
| 69 | |
| 70 | |
| 71 | Note that this technique should only be used after the other options. Due to the way that the JMD pulls records out of the queue table, more recent observations will take precidence. |
| 72 | |