Difference between revisions of "VbzCart/queries/qryCache Flow Procs"

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
Jump to navigation Jump to search
(history and sql updates)
(more specific purpose)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
==About==
 
==About==
* '''Purpose''': compiles caching data for quicker processing
+
* '''Purpose''': gives a list of procs for a given table, making sure that any proc with a set "doesClear" flag comes before the rest.
 
* '''Requires''': {{vbzcart|table|cache_flow}}, {{vbzcart|table|cache_queries}}
 
* '''Requires''': {{vbzcart|table|cache_flow}}, {{vbzcart|table|cache_queries}}
 
* '''Used by''': cache manager
 
* '''Used by''': cache manager
 
* '''History''':
 
* '''History''':
 
** '''2010-11-09''' Renamed tables, so had to fix this query; renamed from v_data_flow to qryCache_Flow_Queries
 
** '''2010-11-09''' Renamed tables, so had to fix this query; renamed from v_data_flow to qryCache_Flow_Queries
 +
** '''2010-11-13''' Renamed from qryCache_Flow_Queries to qryCache_Flow_Procs; modified to use new cache_flow structure
 
==SQL==
 
==SQL==
<section begin=sql /><mysql>CREATE OR REPLACE VIEW qryCache_Flow_Queries AS
+
<section begin=sql /><mysql>CREATE OR REPLACE VIEW qryCache_Flow_Procs AS
 
   SELECT
 
   SELECT
     df.ID_Srce,
+
     cf.ID_Proc,
     df.ID_Dest,
+
     cf.ID_Table,
     df.ID_Proc,
+
     cf.doWrite,
     dfx.doesClear
+
     cp.doesClear
   FROM cache_flow AS df LEFT JOIN cache_queries AS dfx ON df.ID_Proc=dfx.ID
+
   FROM cache_flow AS cf LEFT JOIN cache_queries AS cp ON cf.ID_Proc=cp.ID
   ORDER BY dfx.doesClear;</mysql>
+
   ORDER BY cp.doesClear;</mysql>
 
<section end=sql />
 
<section end=sql />

Latest revision as of 03:14, 14 November 2010

About

  • Purpose: gives a list of procs for a given table, making sure that any proc with a set "doesClear" flag comes before the rest.
  • Requires: cache_flow, cache_queries
  • Used by: cache manager
  • History:
    • 2010-11-09 Renamed tables, so had to fix this query; renamed from v_data_flow to qryCache_Flow_Queries
    • 2010-11-13 Renamed from qryCache_Flow_Queries to qryCache_Flow_Procs; modified to use new cache_flow structure

SQL

<mysql>CREATE OR REPLACE VIEW qryCache_Flow_Procs AS

 SELECT
   cf.ID_Proc,
   cf.ID_Table,
   cf.doWrite,
   cp.doesClear
 FROM cache_flow AS cf LEFT JOIN cache_queries AS cp ON cf.ID_Proc=cp.ID
 ORDER BY cp.doesClear;</mysql>