VbzCart/tables/stk history - Revision history

Woozle: updated syntax highlighting tags

2020-02-03T15:59:25Z

updated syntax highlighting tags

← Older revision		Revision as of 15:59, 3 February 2020
Line 48:		Line 48:
	* The IDS_Line* fields are somewhat redundant, but I decided that redundancy was a goal: one of the purposes of history data (including stk_history) is to help reconstruct what happened when something goes wrong. Maintenance of the _stk_containers table is also somewhat redundant, but should make displaying meaningful history reports quicker (i.e. it's basically a sort of cache, as are all the _* tables).		* The IDS_Line* fields are somewhat redundant, but I decided that redundancy was a goal: one of the purposes of history data (including stk_history) is to help reconstruct what happened when something goes wrong. Maintenance of the _stk_containers table is also somewhat redundant, but should make displaying meaningful history reports quicker (i.e. it's basically a sort of cache, as are all the _* tables).
	==SQL==		==SQL==
	<mysql>CREATE TABLE `stk_history` (		<source lang=mysql>CREATE TABLE `stk_history` (
	`ID` INT NOT NULL AUTO_INCREMENT,		`ID` INT NOT NULL AUTO_INCREMENT,
	`ID_Event` INT DEFAULT NULL COMMENT "ID of corresponding event in unified log",		`ID_Event` INT DEFAULT NULL COMMENT "ID of corresponding event in unified log",
Line 71:		Line 71:
	`Notes` TINYTEXT COMMENT "optional human-added explanatory notes",		`Notes` TINYTEXT COMMENT "optional human-added explanatory notes",
	PRIMARY KEY(`ID`)		PRIMARY KEY(`ID`)
	) ENGINE = INNODB;</~~mysql~~>		) ENGINE = INNODB;</source>
	===Migration===		===Migration===
	The following was used to migrate records from what is now "stk_history OLD 2":		The following was used to migrate records from what is now "stk_history OLD 2":
	<mysql>INSERT INTO stk_history_new (		<source lang=mysql>INSERT INTO stk_history_new (
	ID_Event,		ID_Event,
	ID_StkBin,		ID_StkBin,
Line 117:		Line 117:
	WhoNetwork,		WhoNetwork,
	Notes		Notes
	FROM stk_history</~~mysql~~>		FROM stk_history</source>
	There were no errors or warnings.		There were no errors or warnings.

Woozle: /* History */ template renamed

2017-06-03T16:01:36Z

History: template renamed

← Older revision		Revision as of 16:01, 3 June 2017
Line 31:		Line 31:
	** +CH_OthType		** +CH_OthType
	** +ID_OthCont		** +ID_OthCont
	** Created {{vbzcart/table\|stk_history_legacy}} to handle legacy data properly; turned on all NOT NULLs		** Created {{l/vbzcart/table\|stk_history_legacy}} to handle legacy data properly; turned on all NOT NULLs
	* '''2009-12-20''' Added fields WhoAdmin, WhoSystem, WhoNetwork		* '''2009-12-20''' Added fields WhoAdmin, WhoSystem, WhoNetwork
	* '''2009-12-22''' Renamed When -> WhenStarted; added WhenFinished; QtyAfter and QtyBinAfter can now be NULL so we can record them when the event is complete.		* '''2009-12-22''' Renamed When -> WhenStarted; added WhenFinished; QtyAfter and QtyBinAfter can now be NULL so we can record them when the event is complete.
Line 44:		Line 44:
	*** I decided it was better to tolerate incomplete event-record data than to risk losing the record altogether when an event-write attempt doesn't include all the required fields, since there's currently no guarantee that a failed write will generate an alert anywhere.		*** I decided it was better to tolerate incomplete event-record data than to risk losing the record altogether when an event-write attempt doesn't include all the required fields, since there's currently no guarantee that a failed write will generate an alert anywhere.
	** Officially changing engine to INNODB. Migrated data from stk_history_legacy and then (what is now) `stk_history OLD 2`.		** Officially changing engine to INNODB. Migrated data from stk_history_legacy and then (what is now) `stk_history OLD 2`.

	==Notes==		==Notes==
	* The IDS_Line* fields are somewhat redundant, but I decided that redundancy was a goal: one of the purposes of history data (including stk_history) is to help reconstruct what happened when something goes wrong. Maintenance of the _stk_containers table is also somewhat redundant, but should make displaying meaningful history reports quicker (i.e. it's basically a sort of cache, as are all the _* tables).		* The IDS_Line* fields are somewhat redundant, but I decided that redundancy was a goal: one of the purposes of history data (including stk_history) is to help reconstruct what happened when something goes wrong. Maintenance of the _stk_containers table is also somewhat redundant, but should make displaying meaningful history reports quicker (i.e. it's basically a sort of cache, as are all the _* tables).

Woozle: /* Fields */ templates renamed

2017-06-03T16:00:41Z

Fields: templates renamed

← Older revision		Revision as of 16:00, 3 June 2017
Line 7:		Line 7:

	==Fields==		==Fields==
	* '''CH_OthType''': appropriate type code -- see {{vbzcart/query\|qryStock_containers}} for codes		* '''CH_OthType''': appropriate type code -- see {{l/vbzcart/query\|qryStock_containers}} for codes
	* '''IDS_OthCont''': type code plus separator (period) plus ID unique to that type		* '''IDS_OthCont''': type code plus separator (period) plus ID unique to that type
	* '''ID_Event''': where known, this is the ID of the corresponding event in {{vbzcart\|table\|event_log}}		* '''ID_Event''': where known, this is the ID of the corresponding event in {{l/vbzcart/table\|event_log}}
	** This is a sort of first step towards making this log part of the unified event log.		** This is a sort of first step towards making this log part of the unified event log.
	* '''WhoSystem''': is optional and possibly redundant, but seems to be useful for marking imported/migrated records.		* '''WhoSystem''': is optional and possibly redundant, but seems to be useful for marking imported/migrated records.
Line 15:		Line 15:
	'''Future''':		'''Future''':
	* Rename '''QtyBefore''' and '''QtyAfter''' to QtyLineBefore and QtyLineAfter.		* Rename '''QtyBefore''' and '''QtyAfter''' to QtyLineBefore and QtyLineAfter.

	==History==		==History==
	* '''2008-12-26''' Changed field names, added new fields:		* '''2008-12-26''' Changed field names, added new fields:

Woozle: /* About */ templates renamed

2017-06-03T16:00:09Z

About: templates renamed

← Older revision		Revision as of 16:00, 3 June 2017
Line 1:		Line 1:
	==About==		==About==
	* '''Purpose''': log of all stock movement		* '''Purpose''': log of all stock movement
	* '''Refers to''': {{vbzcart/query\|qryStock_containers}}, {{vbzcart/table\|cat_items}}		* '''Refers to''': {{l/vbzcart/query\|qryStock_containers}}, {{l/vbzcart/table\|cat_items}}
	* '''Rules''':		* '''Rules''':
	** Stock items must always be moved ''to'' or ''from'' a stock line. (The source/destination can be either another stock line or a line from a package or received restock.)		** Stock items must always be moved ''to'' or ''from'' a stock line. (The source/destination can be either another stock line or a line from a package or received restock.)
	** The sign of QtyAdded indicates whether the movement was ''to'' or ''from''.		** The sign of QtyAdded indicates whether the movement was ''to'' or ''from''.

	==Fields==		==Fields==
	* '''CH_OthType''': appropriate type code -- see {{vbzcart/query\|qryStock_containers}} for codes		* '''CH_OthType''': appropriate type code -- see {{vbzcart/query\|qryStock_containers}} for codes

Woozle: migration

2016-03-03T22:45:06Z

migration

← Older revision		Revision as of 22:45, 3 March 2016
Line 5:		Line 5:
	** Stock items must always be moved ''to'' or ''from'' a stock line. (The source/destination can be either another stock line or a line from a package or received restock.)		** Stock items must always be moved ''to'' or ''from'' a stock line. (The source/destination can be either another stock line or a line from a package or received restock.)
	** The sign of QtyAdded indicates whether the movement was ''to'' or ''from''.		** The sign of QtyAdded indicates whether the movement was ''to'' or ''from''.
	* '''Fields~~''':~~		==Fields==
	** '''CH_OthType''': appropriate type code -- see {{vbzcart/query\|qryStock_containers}} for codes		* '''CH_OthType''': appropriate type code -- see {{vbzcart/query\|qryStock_containers}} for codes
	** '''IDS_OthCont''': type code plus separator (period) plus ID unique to that type		* '''IDS_OthCont''': type code plus separator (period) plus ID unique to that type
	** '''ID_Event''': where known, this is the ID of the corresponding event in {{vbzcart\|table\|event_log}}		* '''ID_Event''': where known, this is the ID of the corresponding event in {{vbzcart\|table\|event_log}}
	*** This is a sort of first step towards making this log part of the unified event log.		** This is a sort of first step towards making this log part of the unified event log.
	* '''Future''':		* '''WhoSystem''': is optional and possibly redundant, but seems to be useful for marking imported/migrated records.
	** Rename '''QtyBefore''' and '''QtyAfter''' to QtyLineBefore and QtyLineAfter.
			'''Future''':
			* Rename '''QtyBefore''' and '''QtyAfter''' to QtyLineBefore and QtyLineAfter.
	==History==		==History==
	* '''2008-12-26''' Changed field names, added new fields:		* '''2008-12-26''' Changed field names, added new fields:
Line 35:		Line 37:
	* '''2014-06-26''' Lengthened '''What''' from 63 chars to 255 because descriptions were being cut off.		* '''2014-06-26''' Lengthened '''What''' from 63 chars to 255 because descriptions were being cut off.
	* '''2016-02-24''' Apparently I never changed the actual DB; this time, lengthened '''What''' from 63 chars to TEXT.		* '''2016-02-24''' Apparently I never changed the actual DB; this time, lengthened '''What''' from 63 chars to TEXT.
	* '''2016-03-03''' No NULL values found in ID_StkLine (or in legacy data), so changing it to NOT NULL.		* '''2016-03-03'''
			** No NULL values found in ID_StkLine (or in legacy data), so changing it to NOT NULL.
			** Setting additional NOT NULL fields to DEFAULT NULL in order to accommodate {{l/vc/table\|stk_history_legacy}} data: '''QtyBefore''', '''QtyBinBefore'''
			*** I decided it was better to tolerate incomplete event-record data than to risk losing the record altogether when an event-write attempt doesn't include all the required fields, since there's currently no guarantee that a failed write will generate an alert anywhere.
			** Officially changing engine to INNODB. Migrated data from stk_history_legacy and then (what is now) `stk_history OLD 2`.
	==Notes==		==Notes==
	* The IDS_Line* fields are somewhat redundant, but I decided that redundancy was a goal: one of the purposes of history data (including stk_history) is to help reconstruct what happened when something goes wrong. Maintenance of the _stk_containers table is also somewhat redundant, but should make displaying meaningful history reports quicker (i.e. it's basically a sort of cache, as are all the _* tables).		* The IDS_Line* fields are somewhat redundant, but I decided that redundancy was a goal: one of the purposes of history data (including stk_history) is to help reconstruct what happened when something goes wrong. Maintenance of the _stk_containers table is also somewhat redundant, but should make displaying meaningful history reports quicker (i.e. it's basically a sort of cache, as are all the _* tables).
	==SQL==		==SQL==
	<mysql>CREATE TABLE `stk_history` (		<mysql>CREATE TABLE `stk_history` (
	`ID` INT NOT NULL AUTO_INCREMENT,		`ID` INT NOT NULL AUTO_INCREMENT,
	`ID_Event` INT DEFAULT NULL COMMENT "ID of corresponding event in unified log",		`ID_Event` INT DEFAULT NULL COMMENT "ID of corresponding event in unified log",
	`ID_StkBin` INT NOT NULL COMMENT "stock item is being moved to or from this bin",		`ID_StkBin` INT NOT NULL COMMENT "stock item is being moved to or from this bin",
	`ID_StkLine` INT NOT NULL COMMENT "stk_items.ID of item in this bin being moved",		`ID_StkLine` INT NOT NULL COMMENT "stk_items.ID of item in this bin being moved",
	`CH_OthType` CHAR NOT NULL COMMENT "type for 'other' container & line",		`CH_OthType` CHAR NOT NULL COMMENT "type for 'other' container & line",
	`ID_OthCont` INT DEFAULT NULL COMMENT "[container type's table].ID of the Other place",		`ID_OthCont` INT DEFAULT NULL COMMENT "[container type's table].ID of the Other place",
	`ID_OthLine` INT DEFAULT NULL COMMENT "[container type's line table].ID of of the Other place",		`ID_OthLine` INT DEFAULT NULL COMMENT "[container type's line table].ID of of the Other place",
	`IDS_OthCont` VARCHAR(31) DEFAULT NULL COMMENT "container.IDS of the Other place",		`IDS_OthCont` VARCHAR(31) DEFAULT NULL COMMENT "container.IDS of the Other place",
	`ID_Item` INT NOT NULL COMMENT "cat_items.ID of item being moved",		`ID_Item` INT NOT NULL COMMENT "cat_items.ID of item being moved",
	`QtyBefore` INT ~~NOT~~ NULL COMMENT "quantity found in this stock line ~~before the move",~~		`QtyBefore` INT DEFAULT NULL COMMENT "quantity found in this stock line before the move",
	~~`QtyBinBefore` INT NOT NULL COMMENT "quantity of this ID_Item in the current bin~~ before the move",		`QtyAdded` INT NOT NULL COMMENT "quantity moved (Qty fields at targ/dest may change value later)",
	`QtyAdded` INT NOT NULL COMMENT "quantity moved (Qty fields at targ/dest may change value later)",
	`QtyAfter` INT DEFAULT NULL COMMENT "quantity remaining in this stock line after the move",		`QtyAfter` INT DEFAULT NULL COMMENT "quantity remaining in this stock line after the move",
			`QtyBinBefore` INT DEFAULT NULL COMMENT "quantity of this ID_Item in the current bin before the move",
	`QtyBinAfter` INT DEFAULT NULL COMMENT "quantity of this ID_Item in the current bin after the move",		`QtyBinAfter` INT DEFAULT NULL COMMENT "quantity of this ID_Item in the current bin after the move",
	`WhenStarted` DATETIME NOT NULL COMMENT "when the move was started",		`WhenStarted` DATETIME NOT NULL COMMENT "when the move was started",
Line 59:		Line 65:
	`WhoAdmin` VARCHAR(127) NOT NULL COMMENT "VbzCart admin username",		`WhoAdmin` VARCHAR(127) NOT NULL COMMENT "VbzCart admin username",
	`WhoSystem` VARCHAR(127) DEFAULT NULL COMMENT "who logged into the operating system, if using non-web client app",		`WhoSystem` VARCHAR(127) DEFAULT NULL COMMENT "who logged into the operating system, if using non-web client app",
	`WhoNetwork` VARCHAR(64) COMMENT "network name or IP address of client machine",		`WhoNetwork` VARCHAR(64) NOT NULL COMMENT "network name or IP address of client machine",
	`Notes` TINYTEXT COMMENT "optional human-added explanatory notes",		`Notes` TINYTEXT COMMENT "optional human-added explanatory notes",
	PRIMARY KEY(`ID`)		PRIMARY KEY(`ID`)
	) ENGINE = ~~MYISAM~~;</mysql>		) ENGINE = INNODB;</mysql>
			===Migration===
			The following was used to migrate records from what is now "stk_history OLD 2":
			<mysql>INSERT INTO stk_history_new (
			ID_Event,
			ID_StkBin,
			ID_StkLine,
			CH_OthType,
			ID_OthCont,
			ID_OthLine,
			IDS_OthCont,
			ID_Item,
			QtyBefore,
			QtyAdded,
			QtyAfter,
			QtyBinBefore,
			QtyBinAfter,
			WhenStarted,
			WhenFinished,
			What,
			WhoAdmin,
			WhoSystem,
			WhoNetwork,
			Notes
			)
			SELECT
			ID_Event,
			ID_StkBin,
			ID_StkLine,
			CH_OthType,
			ID_OthCont,
			ID_OthLine,
			IDS_OthCont,
			ID_Item,
			QtyBefore,
			QtyAdded,
			QtyAfter,
			QtyBinBefore,
			QtyBinAfter,
			WhenStarted,
			WhenFinished,
			What,
			WhoAdmin,
			'from old stk_history',
			WhoNetwork,
			Notes
			FROM stk_history</mysql>
			There were no errors or warnings.

Woozle: small change

2016-03-03T21:22:50Z

small change

← Older revision		Revision as of 21:22, 3 March 2016
Line 35:		Line 35:
	* '''2014-06-26''' Lengthened '''What''' from 63 chars to 255 because descriptions were being cut off.		* '''2014-06-26''' Lengthened '''What''' from 63 chars to 255 because descriptions were being cut off.
	* '''2016-02-24''' Apparently I never changed the actual DB; this time, lengthened '''What''' from 63 chars to TEXT.		* '''2016-02-24''' Apparently I never changed the actual DB; this time, lengthened '''What''' from 63 chars to TEXT.
			* '''2016-03-03''' No NULL values found in ID_StkLine (or in legacy data), so changing it to NOT NULL.
	==Notes==		==Notes==
	* The IDS_Line* fields are somewhat redundant, but I decided that redundancy was a goal: one of the purposes of history data (including stk_history) is to help reconstruct what happened when something goes wrong. Maintenance of the _stk_containers table is also somewhat redundant, but should make displaying meaningful history reports quicker (i.e. it's basically a sort of cache, as are all the _* tables).		* The IDS_Line* fields are somewhat redundant, but I decided that redundancy was a goal: one of the purposes of history data (including stk_history) is to help reconstruct what happened when something goes wrong. Maintenance of the _stk_containers table is also somewhat redundant, but should make displaying meaningful history reports quicker (i.e. it's basically a sort of cache, as are all the _* tables).
Line 42:		Line 43:
	`ID_Event` INT DEFAULT NULL COMMENT "ID of corresponding event in unified log",		`ID_Event` INT DEFAULT NULL COMMENT "ID of corresponding event in unified log",
	`ID_StkBin` INT NOT NULL COMMENT "stock item is being moved to or from this bin",		`ID_StkBin` INT NOT NULL COMMENT "stock item is being moved to or from this bin",
	`ID_StkLine` INT ~~DEFAULT~~ NULL COMMENT "stk_items.ID of item in this bin being moved",		`ID_StkLine` INT NOT NULL COMMENT "stk_items.ID of item in this bin being moved",
	`CH_OthType` CHAR NOT NULL COMMENT "type for 'other' container & line",		`CH_OthType` CHAR NOT NULL COMMENT "type for 'other' container & line",
	`ID_OthCont` INT DEFAULT NULL COMMENT "[container type's table].ID of the Other place",		`ID_OthCont` INT DEFAULT NULL COMMENT "[container type's table].ID of the Other place",

Woozle: /* SQL / QtyAfter fields are explicitly DEFAULT NULL

2016-03-02T21:20:24Z

SQL: Qty*After fields are explicitly DEFAULT NULL

← Older revision		Revision as of 21:20, 2 March 2016
Line 51:		Line 51:
	`QtyBinBefore` INT NOT NULL COMMENT "quantity of this ID_Item in the current bin before the move",		`QtyBinBefore` INT NOT NULL COMMENT "quantity of this ID_Item in the current bin before the move",
	`QtyAdded` INT NOT NULL COMMENT "quantity moved (Qty fields at targ/dest may change value later)",		`QtyAdded` INT NOT NULL COMMENT "quantity moved (Qty fields at targ/dest may change value later)",
	`QtyAfter` INT DEFAULT COMMENT "quantity remaining in this stock line after the move",		`QtyAfter` INT DEFAULT NULL COMMENT "quantity remaining in this stock line after the move",
	`QtyBinAfter` INT DEFAULT COMMENT "quantity of this ID_Item in the current bin after the move",		`QtyBinAfter` INT DEFAULT NULL COMMENT "quantity of this ID_Item in the current bin after the move",
	`WhenStarted` DATETIME NOT NULL COMMENT "when the move was started",		`WhenStarted` DATETIME NOT NULL COMMENT "when the move was started",
	`WhenFinished` DATETIME DEFAULT NULL COMMENT "when the move was completed",		`WhenFinished` DATETIME DEFAULT NULL COMMENT "when the move was completed",

Woozle: "What" modified for real

2016-02-24T21:57:18Z

"What" modified for real

← Older revision		Revision as of 21:57, 24 February 2016
Line 34:		Line 34:
	** Left these as NOT NULL: '''ID_StkBin''', '''CH_OthType''' -- Bins must be explicitly created by an administrator, and we should always know what ''type'' of container the Other is.		** Left these as NOT NULL: '''ID_StkBin''', '''CH_OthType''' -- Bins must be explicitly created by an administrator, and we should always know what ''type'' of container the Other is.
	* '''2014-06-26''' Lengthened '''What''' from 63 chars to 255 because descriptions were being cut off.		* '''2014-06-26''' Lengthened '''What''' from 63 chars to 255 because descriptions were being cut off.
			* '''2016-02-24''' Apparently I never changed the actual DB; this time, lengthened '''What''' from 63 chars to TEXT.
	==Notes==		==Notes==
	* The IDS_Line* fields are somewhat redundant, but I decided that redundancy was a goal: one of the purposes of history data (including stk_history) is to help reconstruct what happened when something goes wrong. Maintenance of the _stk_containers table is also somewhat redundant, but should make displaying meaningful history reports quicker (i.e. it's basically a sort of cache, as are all the _* tables).		* The IDS_Line* fields are somewhat redundant, but I decided that redundancy was a goal: one of the purposes of history data (including stk_history) is to help reconstruct what happened when something goes wrong. Maintenance of the _stk_containers table is also somewhat redundant, but should make displaying meaningful history reports quicker (i.e. it's basically a sort of cache, as are all the _* tables).
Line 55:		Line 55:
	`WhenStarted` DATETIME NOT NULL COMMENT "when the move was started",		`WhenStarted` DATETIME NOT NULL COMMENT "when the move was started",
	`WhenFinished` DATETIME DEFAULT NULL COMMENT "when the move was completed",		`WhenFinished` DATETIME DEFAULT NULL COMMENT "when the move was completed",
	`What` ~~VARCHAR(255)~~ DEFAULT NULL COMMENT "automatic description of operation ~~- brief if possible, but clear~~",		`What` TEXT DEFAULT NULL COMMENT "automatic, succinct description of operation",
	`WhoAdmin` VARCHAR(127) NOT NULL COMMENT "VbzCart admin username",		`WhoAdmin` VARCHAR(127) NOT NULL COMMENT "VbzCart admin username",
	`WhoSystem` VARCHAR(127) DEFAULT NULL COMMENT "who logged into the operating system, if using non-web client app",		`WhoSystem` VARCHAR(127) DEFAULT NULL COMMENT "who logged into the operating system, if using non-web client app",

Woozle: lengthened "What"

2014-06-26T21:10:49Z

lengthened "What"

← Older revision		Revision as of 21:10, 26 June 2014
Line 33:		Line 33:
	* '''2014-05-26''' Made fields DEFAULT NULL instead of NOT NULL so we don't have to know all of them before the event is started: '''ID_StkLine''', '''ID_OthCont''', '''ID_OthLine''', '''IDS_OthCont'''		* '''2014-05-26''' Made fields DEFAULT NULL instead of NOT NULL so we don't have to know all of them before the event is started: '''ID_StkLine''', '''ID_OthCont''', '''ID_OthLine''', '''IDS_OthCont'''
	** Left these as NOT NULL: '''ID_StkBin''', '''CH_OthType''' -- Bins must be explicitly created by an administrator, and we should always know what ''type'' of container the Other is.		** Left these as NOT NULL: '''ID_StkBin''', '''CH_OthType''' -- Bins must be explicitly created by an administrator, and we should always know what ''type'' of container the Other is.
			* '''2014-06-26''' Lengthened '''What''' from 63 chars to 255 because descriptions were being cut off.

	==Notes==		==Notes==
Line 54:		Line 55:
	`WhenStarted` DATETIME NOT NULL COMMENT "when the move was started",		`WhenStarted` DATETIME NOT NULL COMMENT "when the move was started",
	`WhenFinished` DATETIME DEFAULT NULL COMMENT "when the move was completed",		`WhenFinished` DATETIME DEFAULT NULL COMMENT "when the move was completed",
	`What` VARCHAR(63) DEFAULT NULL COMMENT "~~brief~~ automatic description of operation",		`What` VARCHAR(255) DEFAULT NULL COMMENT "automatic description of operation - brief if possible, but clear",
	`WhoAdmin` VARCHAR(127) NOT NULL COMMENT "VbzCart admin username",		`WhoAdmin` VARCHAR(127) NOT NULL COMMENT "VbzCart admin username",
	`WhoSystem` VARCHAR(127) DEFAULT NULL COMMENT "who logged into the operating system, if using non-web client app",		`WhoSystem` VARCHAR(127) DEFAULT NULL COMMENT "who logged into the operating system, if using non-web client app",

Woozle: to do: rename 2 fields

2014-06-03T13:39:38Z

to do: rename 2 fields

← Older revision		Revision as of 13:39, 3 June 2014
Line 10:		Line 10:
	** '''ID_Event''': where known, this is the ID of the corresponding event in {{vbzcart\|table\|event_log}}		** '''ID_Event''': where known, this is the ID of the corresponding event in {{vbzcart\|table\|event_log}}
	*** This is a sort of first step towards making this log part of the unified event log.		*** This is a sort of first step towards making this log part of the unified event log.
			* '''Future''':
			** Rename '''QtyBefore''' and '''QtyAfter''' to QtyLineBefore and QtyLineAfter.
	==History==		==History==
	* '''2008-12-26''' Changed field names, added new fields:		* '''2008-12-26''' Changed field names, added new fields:
Line 46:		Line 48:
	`ID_Item` INT NOT NULL COMMENT "cat_items.ID of item being moved",		`ID_Item` INT NOT NULL COMMENT "cat_items.ID of item being moved",
	`QtyBefore` INT NOT NULL COMMENT "quantity found in this stock line before the move",		`QtyBefore` INT NOT NULL COMMENT "quantity found in this stock line before the move",
			`QtyBinBefore` INT NOT NULL COMMENT "quantity of this ID_Item in the current bin before the move",
	`QtyAdded` INT NOT NULL COMMENT "quantity moved (Qty fields at targ/dest may change value later)",		`QtyAdded` INT NOT NULL COMMENT "quantity moved (Qty fields at targ/dest may change value later)",
	`QtyAfter` INT DEFAULT COMMENT "quantity remaining in this stock line after the move",		`QtyAfter` INT DEFAULT COMMENT "quantity remaining in this stock line after the move",
	~~`QtyBinBefore` INT NOT NULL COMMENT "quantity of this ID_Item in the current bin before the move",~~
	`QtyBinAfter` INT DEFAULT COMMENT "quantity of this ID_Item in the current bin after the move",		`QtyBinAfter` INT DEFAULT COMMENT "quantity of this ID_Item in the current bin after the move",
	`WhenStarted` DATETIME NOT NULL COMMENT "when the move was started",		`WhenStarted` DATETIME NOT NULL COMMENT "when the move was started",