VbzCart/tables/rstk ord line - Revision history

Woozle: one more historical note

2016-03-03T23:47:43Z

one more historical note

← Older revision		Revision as of 23:47, 3 March 2016
Line 13:		Line 13:
	* '''2008-11-07''': Created, according to an earlier note on this page -- but the data goes back to 2002, so there was obviously something preceding it.		* '''2008-11-07''': Created, according to an earlier note on this page -- but the data goes back to 2002, so there was obviously something preceding it.
	* '''2016-03-03''': Determined that it is not currently being used anywhere, but not discarding yet.		* '''2016-03-03''': Determined that it is not currently being used anywhere, but not discarding yet.
			** It was apparently last used in 2008 (for LB-2008-01).
	==SQL==		==SQL==
	<mysql>CREATE TABLE `rstk_ord_line` (		<mysql>CREATE TABLE `rstk_ord_line` (

Woozle: status update

2016-03-03T23:46:11Z

status update

← Older revision		Revision as of 23:46, 3 March 2016
Line 1:		Line 1:
			[[category:VbzCart/tables]]
	==About==		==About==
	~~[[category~~:~~VbzCart/tables]]~~		* '''Status''': Uncertain. Not used at present, but looks potentially useful. Won't know if it's needed until we're back in production again.
	* '''~~Created~~''': ~~2008-11-07~~		* '''Purpose''': Planned distribution of restock items to customer orders. This is more of a historical-log-and-search kind of record than something which is actually part of the process. (Should we get rid of it at some point?)
	* Distribution of restock items to customer orders ~~(planned)~~. This is more of a historical-log-and-search kind of record than something which is actually part of the process. (Should we get rid of it at some point?)		** Search for <s>every time a particular item was restock-requested,</s> and which orders we were trying to fill
	** Search for every time a particular item was restock-requested, and which orders we were trying to fill		*** Note that other tables already provide the first piece of information.
	** Search for every time we tried to restock-request items for a particular order		** Search for every time we tried to restock-request items for a particular order
	** Shows which items in a restock request are for customers; remainder are for stock		** <s>Shows which items in a restock request are for customers; remainder are for stock</s>
			*** Existing fields in restock requests already include this information.
			==Fields==
			* '''ID_OrdLine''' is sort of opportunistic – it isn't always available in legacy data. The functions using this new set of data schemas should always fill it in, however.
			==History==
			* '''2008-11-07''': Created, according to an earlier note on this page -- but the data goes back to 2002, so there was obviously something preceding it.
			* '''2016-03-03''': Determined that it is not currently being used anywhere, but not discarding yet.
	==SQL==		==SQL==
	~~<section begin=sql />~~<mysql>CREATE TABLE `rstk_ord_line` (		<mysql>CREATE TABLE `rstk_ord_line` (
	`ID_RstkReq` INT NOT NULL COMMENT "restock request (rstk_req.ID) which is being used to fulfill the customer's order",		`ID_RstkReq` INT NOT NULL COMMENT "restock request (rstk_req.ID) which is being used to fulfill the customer's order",
	`ID_Order` INT NOT NULL COMMENT "customer order (core_orders.ID) which is being fulfilled by this restock request line",		`ID_Order` INT NOT NULL COMMENT "customer order (core_orders.ID) which is being fulfilled by this restock request line",
Line 17:		Line 24:
	)		)
	ENGINE = MYISAM;</mysql>		ENGINE = MYISAM;</mysql>
	~~<section end=sql />~~
	~~==Notes==~~
	* '''ID_OrdLine''' is sort of opportunistic – it isn't always available in legacy data. The functions using this new set of data schemas should always fill it in, however.

Woozle: /* SQL */ changed indexes - ID_RstkReq+ID_Order+ID_Item, since ID_OrdItem isn't always available

2008-11-09T22:41:04Z

SQL: changed indexes - ID_RstkReq+ID_Order+ID_Item, since ID_OrdItem isn't always available

← Older revision		Revision as of 22:41, 9 November 2008
Line 8:		Line 8:
	==SQL==		==SQL==
	<section begin=sql /><mysql>CREATE TABLE `rstk_ord_line` (		<section begin=sql /><mysql>CREATE TABLE `rstk_ord_line` (
	`ID_RstkReq` INT NOT NULL COMMENT "restock request (rstk_req.ID) which is being used to fulfill the customer's order",		`ID_RstkReq` INT NOT NULL COMMENT "restock request (rstk_req.ID) which is being used to fulfill the customer's order",
	`ID_Order` INT NOT NULL COMMENT "customer order (core_orders.ID) which is being fulfilled by this restock request line",		`ID_Order` INT NOT NULL COMMENT "customer order (core_orders.ID) which is being fulfilled by this restock request line",
	`ID_OrdLine` INT ~~NOT~~ NULL COMMENT "specific order line (ord_lines.ID) being fulfilled",		`ID_OrdLine` INT DEFAULT NULL COMMENT "specific order line (ord_lines.ID) being fulfilled",
	`ID_Item` INT NOT NULL COMMENT "item which is being requested to fill the customer's order",		`ID_Item` INT NOT NULL COMMENT "item which is being requested to fill the customer's order",
	`QtyOrd` INT NOT NULL COMMENT "Quantity allocated to this ~~customer~~",		`QtyOrd` INT NOT NULL COMMENT "Quantity of item allocated to this order",
	`Notes` VARCHAR(255) COMMENT "human-entered notes on this allocation item",		`Notes` VARCHAR(255) COMMENT "human-entered notes on this allocation item",
	PRIMARY KEY(`ID_RstkReq`,`~~ID_OrdLine~~`)		PRIMARY KEY(`ID_RstkReq`,`ID_Order`, `ID_Item`)
	)		)
	ENGINE = MYISAM;</mysql>		ENGINE = MYISAM;</mysql>
	<section end=sql />		<section end=sql />
			==Notes==
			* '''ID_OrdLine''' is sort of opportunistic – it isn't always available in legacy data. The functions using this new set of data schemas should always fill it in, however.

Woozle: +ID_Order, ID_RstkLine -> ID_RstkReq, +ID_Item

2008-11-09T16:03:47Z

+ID_Order, ID_RstkLine -> ID_RstkReq, +ID_Item

← Older revision		Revision as of 16:03, 9 November 2008
Line 2:		Line 2:
	[[category:VbzCart/tables]]		[[category:VbzCart/tables]]
	* '''Created''': 2008-11-07		* '''Created''': 2008-11-07
	* Distribution of restock items to customer orders (planned). This is more of a historical-log kind of record than something which is actually part of the process. (Should we get rid of it at some point?)		* Distribution of restock items to customer orders (planned). This is more of a historical-log-and-search kind of record than something which is actually part of the process. (Should we get rid of it at some point?)
			** Search for every time a particular item was restock-requested, and which orders we were trying to fill
			** Search for every time we tried to restock-request items for a particular order
			** Shows which items in a restock request are for customers; remainder are for stock
	==SQL==		==SQL==
	<section begin=sql /><mysql>CREATE TABLE `rstk_ord_line` (		<section begin=sql /><mysql>CREATE TABLE `rstk_ord_line` (
	`~~ID_RstkLine~~` INT NOT NULL COMMENT "~~rstk_line~~.ID which is being used to fulfill the customer's order",		`ID_RstkReq` INT NOT NULL COMMENT "restock request (rstk_req.ID) which is being used to fulfill the customer's order",
	`~~ID_OrdLine~~` INT NOT NULL COMMENT "~~ord_lines~~.ID which is being fulfilled by this restock request line",		`ID_Order` INT NOT NULL COMMENT "customer order (core_orders.ID) which is being fulfilled by this restock request line",
	`QtyOrd` INT NOT NULL COMMENT "Quantity ~~ordered by~~ this customer",		`ID_OrdLine` INT NOT NULL COMMENT "specific order line (ord_lines.ID) being fulfilled",
	`Notes` VARCHAR(255) COMMENT "human-entered notes on this ~~line~~ item",		`ID_Item` INT NOT NULL COMMENT "item which is being requested to fill the customer's order",
	PRIMARY KEY(`~~ID_RstkLine~~`,`ID_OrdLine`)		`QtyOrd` INT NOT NULL COMMENT "Quantity allocated to this customer",
			`Notes` VARCHAR(255) COMMENT "human-entered notes on this allocation item",
			PRIMARY KEY(`ID_RstkReq`,`ID_OrdLine`)
	)		)
	ENGINE = MYISAM;</mysql>		ENGINE = MYISAM;</mysql>
	<section end=sql />		<section end=sql />

Woozle: /* SQL */ replaced missing comma

2008-11-08T02:02:15Z

SQL: replaced missing comma

← Older revision		Revision as of 02:02, 8 November 2008
Line 7:		Line 7:
	`ID_RstkLine` INT NOT NULL COMMENT "rstk_line.ID which is being used to fulfill the customer's order",		`ID_RstkLine` INT NOT NULL COMMENT "rstk_line.ID which is being used to fulfill the customer's order",
	`ID_OrdLine` INT NOT NULL COMMENT "ord_lines.ID which is being fulfilled by this restock request line",		`ID_OrdLine` INT NOT NULL COMMENT "ord_lines.ID which is being fulfilled by this restock request line",
	`QtyOrd` INT NOT NULL COMMENT "Quantity ordered by this customer"		`QtyOrd` INT NOT NULL COMMENT "Quantity ordered by this customer",
	`Notes` VARCHAR(255) COMMENT "human-entered notes on this line item",		`Notes` VARCHAR(255) COMMENT "human-entered notes on this line item",
	PRIMARY KEY(`ID_RstkLine`,`ID_OrdLine`)		PRIMARY KEY(`ID_RstkLine`,`ID_OrdLine`)

Woozle: draft

2008-11-07T18:09:30Z

draft

New page

==About==
[[category:VbzCart/tables]]
* '''Created''': 2008-11-07
* Distribution of restock items to customer orders (planned). This is more of a historical-log kind of record than something which is actually part of the process. (Should we get rid of it at some point?)
==SQL==
<section begin=sql /><mysql>CREATE TABLE `rstk_ord_line` (
`ID_RstkLine` INT NOT NULL COMMENT "rstk_line.ID which is being used to fulfill the customer's order",
`ID_OrdLine` INT NOT NULL COMMENT "ord_lines.ID which is being fulfilled by this restock request line",
`QtyOrd` INT NOT NULL COMMENT "Quantity ordered by this customer"
`Notes` VARCHAR(255) COMMENT "human-entered notes on this line item",
PRIMARY KEY(`ID_RstkLine`,`ID_OrdLine`)
)
ENGINE = MYISAM;</mysql>
<section end=sql />