VbzCart/docs/tables/cat supp: Difference between revisions

From Woozle Writes Code
< VbzCart‎ | docs‎ | tables
Jump to navigation Jump to search
imported>Woozle
(extracted from "tables" page)
 
imported>Woozle
(added ID_Topic field)
Line 1: Line 1:
==About==
==About==
* '''Purpose''': catalog suppliers (i.e. manufacturers, wholesalers)
* '''purpose''': catalog suppliers (i.e. manufacturers, wholesalers)
* '''Future''':
* '''history''':
** '''2011-09-28''' added '''ID_Topic''' field
* '''fields''':
** '''ID_Topic''': subtopics within this topic will take the place of Departments... or at least that is the current thinking
* '''future''':
** Fields which may be added later (or maybe they should be in a separate table):
** Fields which may be added later (or maybe they should be in a separate table):
*** '''MinCostPerOrd''' - currency -- supplier's minimum order, dollar amount
*** '''MinCostPerOrd''' - currency -- supplier's minimum order, dollar amount
Line 12: Line 16:
   `ID` INT  NOT NULL AUTO_INCREMENT,
   `ID` INT  NOT NULL AUTO_INCREMENT,
   `Name`    VARCHAR(64) COMMENT 'name of supplier as displayed',
   `Name`    VARCHAR(64) COMMENT 'name of supplier as displayed',
  `ID_Topic` INT DEFAULT NULL COMMENT "cat_topic.ID of root topic for this supplier",
   `CatKey`  VARCHAR(4) COMMENT 'unique code, used for building catalog numbers',
   `CatKey`  VARCHAR(4) COMMENT 'unique code, used for building catalog numbers',
   `isActive` BOOL COMMENT 'if FALSE, hide from casual listings',
   `isActive` BOOL COMMENT 'if FALSE, hide from casual listings',

Revision as of 23:33, 28 September 2011

About

  • purpose: catalog suppliers (i.e. manufacturers, wholesalers)
  • history:
    • 2011-09-28 added ID_Topic field
  • fields:
    • ID_Topic: subtopics within this topic will take the place of Departments... or at least that is the current thinking
  • future:
    • Fields which may be added later (or maybe they should be in a separate table):
      • MinCostPerOrd - currency -- supplier's minimum order, dollar amount
      • MinQtyPerDesign - int(4) -- supplier's default minimum order per design (can be overridden for specific Titles)
    • Additional contact data should probably be wiki-based. We'll have a namespace for vbz catalog data, probably "vbzcat:", and supplier information will be stored in pages named something like "vbzcat:lb.page", "vbzcat:lb.address", "vbzcat:lb.phone", and so on.
    • There are additional fields in the Access version of this table, but they will be added only when it becomes clear that they are necessary and that there isn't someplace better for them to go.
    • view "suppliers" was a temporary alias of cat_supp but I've renamed it (2008-12-06); anything still using it should use cat_supp instead

SQL

<section begin=sql /><mysql>CREATE TABLE `cat_supp` (

  `ID` INT  NOT NULL AUTO_INCREMENT,
  `Name`     VARCHAR(64) COMMENT 'name of supplier as displayed',
  `ID_Topic` INT DEFAULT NULL COMMENT "cat_topic.ID of root topic for this supplier",
  `CatKey`   VARCHAR(4) COMMENT 'unique code, used for building catalog numbers',
  `isActive` BOOL COMMENT 'if FALSE, hide from casual listings',
  `Notes`    TEXT COMMENT "Human-entered notes about this supplier, for quick reference",
  PRIMARY KEY(`ID`)
)
ENGINE = MYISAM;</mysql>

<section end=sql />