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_.)
- /deprecated: queries we're trying to get rid of, once we're sure nothing uses them
- /discarded: queries apparently no longer in use
- /qryTitles_Imageless - titles with no active images
- /qryCat_Titles_Item_stats -- item/stock statistics
- /qryCat_Titles_Item_count -- simpler query for maintenance
- /qryCat_Items_Stock: cat_items with stock info
- /qryImgs_byTitle: Image info by Title
- /qryCat_pages: maps http path info to catalog entities
- /qryItems_prices: what uses this?
- building process:
- titles x topics:
- for reports:
- all restock requests:
- filtered by status:
This was the first batch of queries I created, before I had decided to go with the qry prefix as in Access.
Caching should only be used for catalog display.