Difference between revisions of "VbzCart/queries"

Revision as of 22:59, 2 March 2016

Navigation

Overview

What MS Access calls "queries" are called "views" in MySQL, i.e. they pull data from existing tables and are themselves usable as data sources in much the same way that tables are (and in which result sets from functions are not).

Some common prefixes:

qryCbx_: queries used for filling comboboxes. The unique ID will always be the first field, and the text to display will always be the second field; additional fields may be provided for use in further qryCbx_ queries which show a subset of the results.
qryCat_: queries which build catalog numbers or information by joining multiple tables. (In Access, the convention was qryCatNum_.)

by category

Inactive

/deprecated: queries we're trying to get rid of, once we're sure nothing uses them
/discarded: queries apparently no longer in use

Catalog

/qryCat_Depts
Title-centric:
- /qryTitles_Item_info
- /qryTitles_ItTyps_grpItems
- /qryTitles_ItTyps_ItTyps
- /qryTitles_ItTyps_Titles
- /qryTitles_Imageless - titles with no active images
- /qryCat_Titles
- /qryCat_Titles_Item_stats -- item/stock statistics
- /qryCat_Titles_Item_count -- simpler query for maintenance
- /qryCat_Titles_web
- /qryCbx_Titles
Item-centric:
- /qryCat_Items_Stock: cat_items with stock info
ItTyp-centric:
- /qryItTypsDepts_grpItems
- /qryItTypsDepts_ItTyps
Image-centric:
- /qryImgs_byTitle: Image info by Title
/qryCat_pages: maps http path info to catalog entities

Catalog Items

/qryCbx_Items_data
- /qryCbx_Items
- /qryCbx_Items_active
- /qryCbx_Items_for_sale
- /qryCbx_Items_opt: abbreviated version for contexts where Title is already known
/qryItems_prices: what uses this?

Catalog Sources

Catalog Topics

titles x topics:
- /qryTitleTopic_Titles: more title information
- /qryTitleTopic_Topics: more topic information
- /qryTitleTopic_Title_avail: title availability information

Ordering

Carts

/qryCarts_info
- /qrySub_Carts_info_data
- /qrySub_Carts_info_items

Customers

Orders

Stock

new queries

- /qryStk_items_remaining
- /qryStk_byItem_byBin
  - /qryStk_byItem_byBin_wInfo

/qryStk_lines_Title_info
/qryStkItms_for_sale_wItem_data
/qryStock_forOpenOrders
/qryStock_byOpt_andType
/qryStock_by_Opt_Type
/qryStock_by_Supp_Type_Opt - unused (and should be Supp_Opt_Type)
/qryStock_Titles_most_recent

REDIRECT Template:l/vc/table queries:

- /qryStock_containers - generates IDS codes
- /qryStk_History - includes legacy table data

old queries

This was the first batch of queries I created, before I had decided to go with the qry prefix as in Access.

Caching

Caching should only be used for catalog display.

/qryCache_Flow_Procs

@@ Line 102: / Line 102: @@
 * '''filtered by status''':
 ** [[/qryRstks_active]]: not terminated = !(closed, orphaned or killed - see {{l/vc/term|restock/status}})
-*** [[/qryRstkItms_active]]
-**** [[/qryRstkItms_expected]]
-***** [[/qryRstkItms_expected_byItem]] - grouped by ID_Item
 *** [[/qryRstks_unsent]]: created but not ordered yet
 **** [[/qryRstkItms_unsent]]
@@ Line 120: / Line 117: @@
 ** [[/qryStk_lines_remaining_forSale]]
 *** [[/qryStkItms_for_sale]]
-**** [[/qryItems_needed_forStock]]
 ** [[/qryStk_items_remaining]]
 ** [[/qryStk_byItem_byBin]]