VbzCart/queries/qryCache Flow Procs - Revision history

Woozle: more specific purpose

2010-11-14T03:14:53Z

more specific purpose

← Older revision		Revision as of 03:14, 14 November 2010
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

Woozle: one field missing

2010-11-14T02:31:29Z

one field missing

← Older revision		Revision as of 02:31, 14 November 2010
Line 9:		Line 9:
	<section begin=sql /><mysql>CREATE OR REPLACE VIEW qryCache_Flow_Procs AS		<section begin=sql /><mysql>CREATE OR REPLACE VIEW qryCache_Flow_Procs AS
	SELECT		SELECT
	df.ID_Proc,		cf.ID_Proc,
	df.ID_Table,		cf.ID_Table,
	~~dfx~~.doesClear		cf.doWrite,
	FROM cache_flow AS df LEFT JOIN cache_queries AS ~~dfx~~ ON df.ID_Proc=~~dfx~~.ID		cp.doesClear
	ORDER BY ~~dfx~~.doesClear;</mysql>		FROM cache_flow AS cf LEFT JOIN cache_queries AS cp ON cf.ID_Proc=cp.ID
			ORDER BY cp.doesClear;</mysql>
	<section end=sql />		<section end=sql />

Woozle: queries -> procs, new flow structure

2010-11-13T22:26:03Z

queries -> procs, new flow structure

← Older revision		Revision as of 22:26, 13 November 2010
Line 5:		Line 5:
	* '''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,~~
	~~df.ID_Dest,~~
	df.ID_Proc,		df.ID_Proc,
			df.ID_Table,
	dfx.doesClear		dfx.doesClear
	FROM cache_flow AS df LEFT JOIN cache_queries AS dfx ON df.ID_Proc=dfx.ID		FROM cache_flow AS df LEFT JOIN cache_queries AS dfx ON df.ID_Proc=dfx.ID
	ORDER BY dfx.doesClear;</mysql>		ORDER BY dfx.doesClear;</mysql>
	<section end=sql />		<section end=sql />

Woozle: moved VbzCart/queries/qryCache Flow Queries to VbzCart/queries/qryCache Flow Procs: going back to "procs" instead of "queries"

2010-11-13T22:23:49Z

moved VbzCart/queries/qryCache Flow Queries to VbzCart/queries/qryCache Flow Procs: going back to "procs" instead of "queries"

← Older revision	Revision as of 22:23, 13 November 2010
(No difference)

Woozle: history and sql updates

2010-11-09T19:44:19Z

history and sql updates

← Older revision		Revision as of 19:44, 9 November 2010
Line 2:		Line 2:
	* '''Purpose''': compiles caching data for quicker processing		* '''Purpose''': compiles caching data for quicker processing
	* '''Requires''': {{vbzcart\|table\|cache_flow}}, {{vbzcart\|table\|cache_queries}}		* '''Requires''': {{vbzcart\|table\|cache_flow}}, {{vbzcart\|table\|cache_queries}}
	* '''Used by''': ~~store page display routines (need to be more specific...)~~		* '''Used by''': cache manager
	* '''History''':		* '''History''':
	** '''2010-11-09''' Renamed tables, so had to fix this query		** '''2010-11-09''' Renamed tables, so had to fix this query; renamed from v_data_flow to qryCache_Flow_Queries
	==SQL==		==SQL==
	<section begin=sql /><mysql>CREATE OR REPLACE VIEW ~~v_data_flow~~ AS		<section begin=sql /><mysql>CREATE OR REPLACE VIEW qryCache_Flow_Queries AS
	SELECT		SELECT
	df.ID_Srce,		df.ID_Srce,

Woozle: moved VbzCart/queries/v data flow to VbzCart/queries/qryCache Flow Queries: using more canonical naming convention

2010-11-09T19:27:32Z

moved VbzCart/queries/v data flow to VbzCart/queries/qryCache Flow Queries: using more canonical naming convention

← Older revision	Revision as of 19:27, 9 November 2010
(No difference)

Woozle: correct header

2010-11-09T18:21:45Z

correct header

← Older revision		Revision as of 18:21, 9 November 2010
Line 5:		Line 5:
	* '''History''':		* '''History''':
	** '''2010-11-09''' Renamed tables, so had to fix this query		** '''2010-11-09''' Renamed tables, so had to fix this query
	==~~==v_data_flow==~~==		==SQL==
	<section begin=sql /><mysql>CREATE OR REPLACE VIEW v_data_flow AS		<section begin=sql /><mysql>CREATE OR REPLACE VIEW v_data_flow AS
	SELECT		SELECT

Woozle: extracted from queries page

2010-11-09T18:21:27Z

extracted from queries page

New page

==About==
* '''Purpose''': compiles caching data for quicker processing
* '''Requires''': {{vbzcart|table|cache_flow}}, {{vbzcart|table|cache_queries}}
* '''Used by''': store page display routines (need to be more specific...)
* '''History''':
** '''2010-11-09''' Renamed tables, so had to fix this query
====v_data_flow====
<section begin=sql /><mysql>CREATE OR REPLACE VIEW v_data_flow AS
SELECT
df.ID_Srce,
df.ID_Dest,
df.ID_Proc,
dfx.doesClear
FROM cache_flow AS df LEFT JOIN cache_queries AS dfx ON df.ID_Proc=dfx.ID
ORDER BY dfx.doesClear;</mysql>
<section end=sql />