VbzCart/queries/qryStk History - Revision history

Woozle: correction

2016-03-03T23:06:10Z

correction

← Older revision		Revision as of 23:06, 3 March 2016
Line 1:		Line 1:
	==About==		==About==
	* '''Status''': No longer functional; dropped. Legacy data was merged into revised {{l/vc/table\|stk_history}}.		* '''Status''': No longer functional; was apparently dropped awhile ago (or not migrated to latest server). Legacy data was merged into revised {{l/vc/table\|stk_history}}.
	* '''Purpose''': {{l/vc/table\|stk_history}} plus {{l/vc/table\|stk_history_legacy}} data, if any, with IDs adjusted to prevent duplicates. Lets you see the complete history including legacy stuff, without polluting the main log with non-fixable legacy data.		* '''Purpose''': {{l/vc/table\|stk_history}} plus {{l/vc/table\|stk_history_legacy}} data, if any, with IDs adjusted to prevent duplicates. Lets you see the complete history including legacy stuff, without polluting the main log with non-fixable legacy data.
	* '''History''':		* '''History''':
	** '''2008-12-29''' Created		** '''2008-12-29''' Created
	** '''2008-12-30''' Added "ORDER BY ID" so everything will be in sequence (apparently ORDER BY is assumed to refer to the whole UNION, and can't be used within the individual SELECTs that go into the UNION)		** '''2008-12-30''' Added "ORDER BY ID" so everything will be in sequence (apparently ORDER BY is assumed to refer to the whole UNION, and can't be used within the individual SELECTs that go into the UNION)
	** '''2016-03-03''' ~~Dropped~~.		** '''2016-03-03''' Officially dropped, though it was already absent from the database.
	==SQL==		==SQL==
	<mysql>CREATE OR REPLACE VIEW qryStk_History AS		<mysql>CREATE OR REPLACE VIEW qryStk_History AS

Woozle: dropped

2016-03-03T23:04:59Z

dropped

← Older revision		Revision as of 23:04, 3 March 2016
Line 1:		Line 1:
	==About==		==About==
	* '''Purpose''': {{~~vbzcart~~/table\|stk_history}} plus {{~~vbzcart~~/table\|stk_history_legacy}} data, if any, with IDs adjusted to prevent duplicates. Lets you see the complete history including legacy stuff, without polluting the main log with non-fixable legacy data.		* '''Status''': No longer functional; dropped. Legacy data was merged into revised {{l/vc/table\|stk_history}}.
			* '''Purpose''': {{l/vc/table\|stk_history}} plus {{l/vc/table\|stk_history_legacy}} data, if any, with IDs adjusted to prevent duplicates. Lets you see the complete history including legacy stuff, without polluting the main log with non-fixable legacy data.
	* '''History''':		* '''History''':
	** '''2008-12-29''' Created		** '''2008-12-29''' Created
	** '''2008-12-30''' Added "ORDER BY ID" so everything will be in sequence (apparently ORDER BY is assumed to refer to the whole UNION, and can't be used within the individual SELECTs that go into the UNION)		** '''2008-12-30''' Added "ORDER BY ID" so everything will be in sequence (apparently ORDER BY is assumed to refer to the whole UNION, and can't be used within the individual SELECTs that go into the UNION)
			** '''2016-03-03''' Dropped.
	==SQL==		==SQL==
	~~<section begin=sql />~~<mysql>CREATE OR REPLACE VIEW qryStk_History AS		<mysql>CREATE OR REPLACE VIEW qryStk_History AS
	SELECT * FROM stk_history		SELECT * FROM stk_history
	UNION		UNION
Line 27:		Line 29:
	FROM stk_history_legacy		FROM stk_history_legacy
	ORDER BY ID;</mysql>		ORDER BY ID;</mysql>
	~~<section end=sql />~~

Woozle: +ORDER BY ID

2008-12-30T17:08:47Z

+ORDER BY ID

← Older revision		Revision as of 17:08, 30 December 2008
Line 3:		Line 3:
	* '''History''':		* '''History''':
	** '''2008-12-29''' Created		** '''2008-12-29''' Created
			** '''2008-12-30''' Added "ORDER BY ID" so everything will be in sequence (apparently ORDER BY is assumed to refer to the whole UNION, and can't be used within the individual SELECTs that go into the UNION)
	==SQL==		==SQL==
	<section begin=sql /><mysql>CREATE OR REPLACE VIEW qryStk_History AS		<section begin=sql /><mysql>CREATE OR REPLACE VIEW qryStk_History AS
Line 24:		Line 25:
	What,		What,
	Notes		Notes
	FROM stk_history_legacy;		FROM stk_history_legacy
	</mysql>		ORDER BY ID;</mysql>
	<section end=sql />		<section end=sql />

Woozle: New page: ==About== * '''Purpose''': {{vbzcart/table|stk_history}} plus {{vbzcart/table|stk_history_legacy}} data, if any, with IDs adjusted to prevent duplicates. Lets you see the complete history ...

2008-12-29T19:15:17Z

New page: ==About== * '''Purpose''': {{vbzcart/table|stk_history}} plus {{vbzcart/table|stk_history_legacy}} data, if any, with IDs adjusted to prevent duplicates. Lets you see the complete history ...

New page

==About==
* '''Purpose''': {{vbzcart/table|stk_history}} plus {{vbzcart/table|stk_history_legacy}} data, if any, with IDs adjusted to prevent duplicates. Lets you see the complete history including legacy stuff, without polluting the main log with non-fixable legacy data.
* '''History''':
** '''2008-12-29''' Created
==SQL==
<section begin=sql /><mysql>CREATE OR REPLACE VIEW qryStk_History AS
SELECT * FROM stk_history
UNION
SELECT
CAST(ID-5000 AS SIGNED) AS ID,
ID_StkBin,
ID_StkLine,
CH_OthType,
ID_OthCont,
ID_OthLine,
IDS_OthCont,
ID_Item,
QtyBefore,
QtyAdded,
QtyAfter,
QtyBinBefore,
QtyBinAfter,
`When`,
What,
Notes
FROM stk_history_legacy;
</mysql>
<section end=sql />