VbzCart/tables/cat titles - Revision history

Woozle: tidying

2016-11-07T19:04:24Z

tidying

Woozle: more room for Notes

2016-01-18T01:05:48Z

more room for Notes

← Older revision		Revision as of 01:05, 18 January 2016
Line 10:		Line 10:
	*** The code doesn't know this yet, but it will get fixed as time permits.		*** The code doesn't know this yet, but it will get fixed as time permits.
	*** Once the code is rewritten and any remaining Dept data is migrated to Topics, we can remove '''ID_Dept'''.		*** Once the code is rewritten and any remaining Dept data is migrated to Topics, we can remove '''ID_Dept'''.
			** '''2016-01-17''' changed '''Notes''' from VARCHAR(255) to TEXT because notes, while rare, are sometimes long.
			*** Eventually, Ferreteria will provide a wiki-like content management API...
	==SQL==		==SQL==
	~~<section begin=sql />~~<mysql> CREATE TABLE `cat_titles` (		<mysql> CREATE TABLE `cat_titles` (
	`ID` int(11) unsigned NOT NULL auto_increment,		`ID` int(11) unsigned NOT NULL auto_increment,
	`Name` varchar(127),		`Name` varchar(127),
Line 26:		Line 28:
	`Desc` tinytext COMMENT 'descriptive text for display on web - DEPRECATED (use wiki)',		`Desc` tinytext COMMENT 'descriptive text for display on web - DEPRECATED (use wiki)',
	`Search` varchar(255) COMMENT 'additional keywords for searching, but not displayed',		`Search` varchar(255) COMMENT 'additional keywords for searching, but not displayed',
	`Notes` ~~varchar(255)~~ COMMENT 'internal notes; not displayed or searched - DEPRECATED (use wiki)',		`Notes` TEXT COMMENT 'internal notes; not displayed or searched - DEPRECATED (use wiki)',
	PRIMARY KEY(`ID`)		PRIMARY KEY(`ID`)
	) ENGINE=MyISAM DEFAULT CHARSET=latin1;</mysql>		) ENGINE=MyISAM DEFAULT CHARSET=latin1;</mysql>
	~~<section end=sql />~~

Woozle: added ID_Supp, modified ID_Dept

2011-09-28T13:22:48Z

added ID_Supp, modified ID_Dept

← Older revision		Revision as of 13:22, 28 September 2011
Line 5:		Line 5:
	** Possibly another field specifically for text that appears in the Title's image(s) -- or should that be tied to the Images data?		** Possibly another field specifically for text that appears in the Title's image(s) -- or should that be tied to the Images data?
	** Also possibly another field for an "alt=" description (what the thing actually looks like, in words)		** Also possibly another field for an "alt=" description (what the thing actually looks like, in words)
	** '''ID_License''' should go with Images (earlier, was thinking this could be tracked as a Topic, but making it image-specific ~~tentatively~~ makes more sense)		** '''ID_License''' should go with Images (earlier, was thinking this could be tracked as a Topic, but making it image-specific makes more sense -- e.g. a photo of a model wearing a shirt should be licensed differently than the image of the pattern that goes on the shirt)
			* '''History''':
			** '''2011-09-28''' adding '''ID_Supp''' field, making '''ID_Dept''' DEFAULT NULL (and optional)
			*** The code doesn't know this yet, but it will get fixed as time permits.
			*** Once the code is rewritten and any remaining Dept data is migrated to Topics, we can remove '''ID_Dept'''.
	==SQL==		==SQL==
	<section begin=sql /><mysql> CREATE TABLE `cat_titles` (		<section begin=sql /><mysql> CREATE TABLE `cat_titles` (
	`ID` int(11) unsigned NOT NULL auto_increment,		`ID` int(11) unsigned NOT NULL auto_increment,
	`Name` varchar(127),		`Name` varchar(127),
	`CatKey` varchar(63) NOT NULL,		`CatKey` varchar(63) NOT NULL,
	`ID_Dept` int(11) ~~unsigned NOT~~ NULL ~~default '0'~~,		`ID_Supp` INT(11) UNSIGNED NOT NULL COMMENT "cat_supp.ID",
	`ID_License` int(11) ~~default~~ NULL COMMENT "DEPRECATED",		`ID_Dept` int(11) UNSIGNED DEFAULT NULL COMMENT "cat_dept.ID (optional)",
	`DateAdded` datetime ~~default~~ NULL,		`ID_License` int(11) DEFAULT NULL COMMENT "DEPRECATED",
	`DateChecked` datetime ~~default~~ NULL COMMENT 'DEPRECATED',		`DateAdded` datetime DEFAULT NULL,
	`DateUnavail` datetime ~~default~~ NULL,		`DateChecked` datetime DEFAULT NULL COMMENT 'DEPRECATED',
	`RstkMin` int(11) unsigned ~~default~~ NULL,		`DateUnavail` datetime DEFAULT NULL,
	`Supplier_CatNum` varchar(31),		`RstkMin` int(11) unsigned DEFAULT NULL COMMENT "minimum qty that can be ordered from supplier",
			`Supplier_CatNum` varchar(31) COMMENT "supplier's catalog # for this title",
	`Supplier_CatNum_Alt` varchar(31) COMMENT 'DEPRECATED',		`Supplier_CatNum_Alt` varchar(31) COMMENT 'DEPRECATED',
	`Desc` tinytext COMMENT 'descriptive text for display on web - DEPRECATED (use wiki)',		`Desc` tinytext COMMENT 'descriptive text for display on web - DEPRECATED (use wiki)',
	`Search` varchar(255) COMMENT 'additional keywords for searching, but not displayed',		`Search` varchar(255) COMMENT 'additional keywords for searching, but not displayed',
	`Notes` varchar(255) COMMENT 'internal notes; not displayed or searched - DEPRECATED (use wiki)',		`Notes` varchar(255) COMMENT 'internal notes; not displayed or searched - DEPRECATED (use wiki)',
	PRIMARY KEY(`ID`)		PRIMARY KEY(`ID`)
	) ENGINE=MyISAM DEFAULT CHARSET=latin1;</mysql>		) ENGINE=MyISAM DEFAULT CHARSET=latin1;</mysql>
	<section end=sql />		<section end=sql />

Woozle: future notes

2011-01-29T18:48:44Z

future notes

← Older revision		Revision as of 18:48, 29 January 2011
Line 2:		Line 2:
	* '''Purpose''': catalog titles within departments		* '''Purpose''': catalog titles within departments
	* '''Future''': The design of this table will probably change some, as there deprecated fields to be removed (note that the extra complication of using the wiki for data must be balanced against the ease-of-editing and flexibility this allows)		* '''Future''': The design of this table will probably change some, as there deprecated fields to be removed (note that the extra complication of using the wiki for data must be balanced against the ease-of-editing and flexibility this allows)
			** Rename '''Desc''' to '''Descr''' because "Desc" is an SQL keyword
			** Possibly another field specifically for text that appears in the Title's image(s) -- or should that be tied to the Images data?
			** Also possibly another field for an "alt=" description (what the thing actually looks like, in words)
			** '''ID_License''' should go with Images (earlier, was thinking this could be tracked as a Topic, but making it image-specific tentatively makes more sense)
	==SQL==		==SQL==
	<section begin=sql /><mysql> CREATE TABLE `cat_titles` (		<section begin=sql /><mysql> CREATE TABLE `cat_titles` (
Line 8:		Line 12:
	`CatKey` varchar(63) NOT NULL,		`CatKey` varchar(63) NOT NULL,
	`ID_Dept` int(11) unsigned NOT NULL default '0',		`ID_Dept` int(11) unsigned NOT NULL default '0',
	`ID_License` int(11) default NULL COMMENT ~~'ID of agency from which the image was licensed -~~ DEPRECATED~~; fileferret will track as topic'~~,		`ID_License` int(11) default NULL COMMENT "DEPRECATED",
	`DateAdded` datetime default NULL,		`DateAdded` datetime default NULL,
	`DateChecked` datetime default NULL COMMENT 'DEPRECATED',		`DateChecked` datetime default NULL COMMENT 'DEPRECATED',

Woozle: extracted from "tables" page

2008-12-06T15:15:22Z

extracted from "tables" page

New page

==About==
* '''Purpose''': catalog titles within departments
* '''Future''': The design of this table will probably change some, as there deprecated fields to be removed (note that the extra complication of using the wiki for data must be balanced against the ease-of-editing and flexibility this allows)
==SQL==
<section begin=sql /><mysql> CREATE TABLE `cat_titles` (
`ID` int(11) unsigned NOT NULL auto_increment,
`Name` varchar(127),
`CatKey` varchar(63) NOT NULL,
`ID_Dept` int(11) unsigned NOT NULL default '0',
`ID_License` int(11) default NULL COMMENT 'ID of agency from which the image was licensed - DEPRECATED; fileferret will track as topic',
`DateAdded` datetime default NULL,
`DateChecked` datetime default NULL COMMENT 'DEPRECATED',
`DateUnavail` datetime default NULL,
`RstkMin` int(11) unsigned default NULL,
`Supplier_CatNum` varchar(31),
`Supplier_CatNum_Alt` varchar(31) COMMENT 'DEPRECATED',
`Desc` tinytext COMMENT 'descriptive text for display on web - DEPRECATED (use wiki)',
`Search` varchar(255) COMMENT 'additional keywords for searching, but not displayed',
`Notes` varchar(255) COMMENT 'internal notes; not displayed or searched - DEPRECATED (use wiki)',
PRIMARY KEY(`ID`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;</mysql>
<section end=sql />

← Older revision		Revision as of 19:04, 7 November 2016
Line 1:		Line 1:
	==About==		==About==
	* '''Purpose''': catalog titles within departments		* '''Purpose''': catalog titles within departments
	* '''Future''': The design of this table will probably change some, as there deprecated fields to be removed ~~(note that the extra complication of using the wiki for data must be balanced against the ease-of-editing and flexibility this allows)~~		* '''Related''': {{vbzcart/table\|cat_depts}} (parent), {{vbzcart/table\|cat_supp}} (parent)
			* '''Future''': The design of this table will probably change some, as there are deprecated fields to be removed
	** Rename '''Desc''' to '''Descr''' because "Desc" is an SQL keyword		** Rename '''Desc''' to '''Descr''' because "Desc" is an SQL keyword
	** Possibly another field specifically for text that appears in the Title's image(s) -- or should that be tied to the Images data?		** Possibly another field specifically for text that appears in the Title's image(s) -- or should that be tied to the Images data?
	** Also possibly another field for an "alt=" description (what the thing actually looks like, in words)		** Also possibly another field for an "alt=" description (what the thing actually looks like, in words)
	** '''ID_License''' should go with Images (earlier, was thinking this could be tracked as a Topic, but making it image-specific makes more sense -- e.g. a photo of a model wearing a shirt should be licensed differently than the image of the pattern that goes on the shirt)		** '''ID_License''' should go with Images (earlier, was thinking this could be tracked as a Topic, but making it image-specific makes more sense -- e.g. a photo of a model wearing a shirt should be licensed differently than the image of the pattern that goes on the shirt)
	* '''History~~''':~~		==History==
	** '''2011-09-28''' adding '''ID_Supp''' field, making '''ID_Dept''' DEFAULT NULL (and optional)		* '''2011-09-28''' adding '''ID_Supp''' field, making '''ID_Dept''' DEFAULT NULL (and optional)
	*** The code doesn't know this yet, but it will get fixed as time permits.		** The code doesn't know this yet, but it will get fixed as time permits.
	*** Once the code is rewritten and any remaining Dept data is migrated to Topics, we can remove '''ID_Dept'''.		** Once the code is rewritten and any remaining Dept data is migrated to Topics, we can remove '''ID_Dept'''.
	** '''2016-01-17''' changed '''Notes''' from VARCHAR(255) to TEXT because notes, while rare, are sometimes long.		* '''2016-01-17''' changed '''Notes''' from VARCHAR(255) to TEXT because notes, while rare, are sometimes long.
	*** Eventually, Ferreteria will provide a wiki-like content management API...		** Eventually, Ferreteria will provide a wiki-like content management API...
	==SQL==		==SQL==
	<mysql> CREATE TABLE `cat_titles` (		<mysql> CREATE TABLE `cat_titles` (