VbzCart/queries/qryRstks active - Revision history

Woozle: obsolete

2015-12-31T18:43:50Z

obsolete

← Older revision		Revision as of 18:43, 31 December 2015
Line 1:		Line 1:
	==Details==		==Details==
			* '''Obsolete''': use '''cRstkReqs::SQLfor_Active_NewestFirst()''' instead
	* '''Returns''': List of restock requests for which we are currently expecting one or more shipments; the exact opposite of {{vbzcart/query\|qryRstks_inactive}}.		* '''Returns''': List of restock requests for which we are currently expecting one or more shipments; the exact opposite of {{vbzcart/query\|qryRstks_inactive}}.
	* '''Requires''': {{vbzcart/table\|rstk_req}}		* '''Requires''': {{vbzcart/table\|rstk_req}}
Line 6:		Line 7:
	** '''2008-11-19''' Created for new restock process		** '''2008-11-19''' Created for new restock process
	** '''2008-11-20''' Including '''WhenClosed''' (new field) in the filter		** '''2008-11-20''' Including '''WhenClosed''' (new field) in the filter
			** '''2015-12-31''' Replacing this with PHP-generated SQL
	* '''Notes''':		* '''Notes''':
	** We don't want to exclude requests just because a shipment has been received, because that shipment might not have included everything in the request. Once a request is marked closed (via '''WhenClosed'''), however, it means we are not expecting any further receipts from that request and we will need to request again if there's anything not yet received.		** We don't want to exclude requests just because a shipment has been received, because that shipment might not have included everything in the request. Once a request is marked closed (via '''WhenClosed'''), however, it means we are not expecting any further receipts from that request and we will need to request again if there's anything not yet received.
	** At one point, doing a JOIN with rstk_rcd seemed to make the query run faster, but this may have been an illusion due to caching by MySQL and not enough testing.		** At one point, doing a JOIN with rstk_rcd seemed to make the query run faster, but this may have been an illusion due to caching by MySQL and not enough testing.
	==SQL==		==SQL==
	~~<section begin=sql />~~<mysql>CREATE OR REPLACE VIEW qryRstks_active AS		<mysql>CREATE OR REPLACE VIEW qryRstks_active AS
	SELECT rq.* FROM rstk_req AS rq		SELECT rq.* FROM rstk_req AS rq
	WHERE (rq.WhenClosed IS NULL) AND (rq.WhenKilled IS NULL) AND (rq.WhenOrphaned IS NULL);</mysql>		WHERE (rq.WhenClosed IS NULL) AND (rq.WhenKilled IS NULL) AND (rq.WhenOrphaned IS NULL);</mysql>
	~~<section end=sql />~~

Woozle: doc: usage, new opposite query

2010-01-03T15:25:10Z

doc: usage, new opposite query

← Older revision		Revision as of 15:25, 3 January 2010
Line 1:		Line 1:
	==Details==		==Details==
	* '''Returns''': List of restock requests for which we are currently expecting one or more shipments		* '''Returns''': List of restock requests for which we are currently expecting one or more shipments; the exact opposite of {{vbzcart/query\|qryRstks_inactive}}.
	* '''Requires''': {{vbzcart/table\|rstk_req}}		* '''Requires''': {{vbzcart/table\|rstk_req}}
	* '''Used by''': {{vbzcart/query\|qryRstkItms_active}}, {{vbzcart/query\|qryRstks_unsent}}		* '''Used by''': {{vbzcart/query\|qryRstkItms_active}}, {{vbzcart/query\|qryRstks_unsent}}, page for displaying expected restocks
	* '''History''':		* '''History''':
	** '''2008-11-19''' Created for new restock process		** '''2008-11-19''' Created for new restock process
Line 9:		Line 9:
	** We don't want to exclude requests just because a shipment has been received, because that shipment might not have included everything in the request. Once a request is marked closed (via '''WhenClosed'''), however, it means we are not expecting any further receipts from that request and we will need to request again if there's anything not yet received.		** We don't want to exclude requests just because a shipment has been received, because that shipment might not have included everything in the request. Once a request is marked closed (via '''WhenClosed'''), however, it means we are not expecting any further receipts from that request and we will need to request again if there's anything not yet received.
	** At one point, doing a JOIN with rstk_rcd seemed to make the query run faster, but this may have been an illusion due to caching by MySQL and not enough testing.		** At one point, doing a JOIN with rstk_rcd seemed to make the query run faster, but this may have been an illusion due to caching by MySQL and not enough testing.

	==SQL==		==SQL==
	<section begin=sql /><mysql>CREATE OR REPLACE VIEW qryRstks_active AS		<section begin=sql /><mysql>CREATE OR REPLACE VIEW qryRstks_active AS

Woozle: /* Details */ used by (2 queries)

2008-12-05T01:46:05Z

Details: used by (2 queries)

← Older revision		Revision as of 01:46, 5 December 2008
Line 2:		Line 2:
	* '''Returns''': List of restock requests for which we are currently expecting one or more shipments		* '''Returns''': List of restock requests for which we are currently expecting one or more shipments
	* '''Requires''': {{vbzcart/table\|rstk_req}}		* '''Requires''': {{vbzcart/table\|rstk_req}}
	* '''Used by''':		* '''Used by''': {{vbzcart/query\|qryRstkItms_active}}, {{vbzcart/query\|qryRstks_unsent}}
	* '''History''':		* '''History''':
	** '''2008-11-19''' Created for new restock process		** '''2008-11-19''' Created for new restock process
Line 9:		Line 9:
	** We don't want to exclude requests just because a shipment has been received, because that shipment might not have included everything in the request. Once a request is marked closed (via '''WhenClosed'''), however, it means we are not expecting any further receipts from that request and we will need to request again if there's anything not yet received.		** We don't want to exclude requests just because a shipment has been received, because that shipment might not have included everything in the request. Once a request is marked closed (via '''WhenClosed'''), however, it means we are not expecting any further receipts from that request and we will need to request again if there's anything not yet received.
	** At one point, doing a JOIN with rstk_rcd seemed to make the query run faster, but this may have been an illusion due to caching by MySQL and not enough testing.		** At one point, doing a JOIN with rstk_rcd seemed to make the query run faster, but this may have been an illusion due to caching by MySQL and not enough testing.

	==SQL==		==SQL==
	<section begin=sql /><mysql>CREATE OR REPLACE VIEW qryRstks_active AS		<section begin=sql /><mysql>CREATE OR REPLACE VIEW qryRstks_active AS

Woozle: New page: ==Details== * '''Returns''': List of restock requests for which we are currently expecting one or more shipments * '''Requires''': {{vbzcart/table|rstk_req}} * '''Used by''': * '''History'...

2008-12-04T00:26:14Z

New page: ==Details== * '''Returns''': List of restock requests for which we are currently expecting one or more shipments * '''Requires''': {{vbzcart/table|rstk_req}} * '''Used by''': * '''History'...

New page

==Details==
* '''Returns''': List of restock requests for which we are currently expecting one or more shipments
* '''Requires''': {{vbzcart/table|rstk_req}}
* '''Used by''':
* '''History''':
** '''2008-11-19''' Created for new restock process
** '''2008-11-20''' Including '''WhenClosed''' (new field) in the filter
* '''Notes''':
** We don't want to exclude requests just because a shipment has been received, because that shipment might not have included everything in the request. Once a request is marked closed (via '''WhenClosed'''), however, it means we are not expecting any further receipts from that request and we will need to request again if there's anything not yet received.
** At one point, doing a JOIN with rstk_rcd seemed to make the query run faster, but this may have been an illusion due to caching by MySQL and not enough testing.
==SQL==
<section begin=sql /><mysql>CREATE OR REPLACE VIEW qryRstks_active AS
SELECT rq.* FROM rstk_req AS rq
WHERE (rq.WhenClosed IS NULL) AND (rq.WhenKilled IS NULL) AND (rq.WhenOrphaned IS NULL);</mysql>
<section end=sql />