User:Woozle/PostFerret/sql/post - Revision history

Woozle: decided that this should point to other Atoms rather than directly to Text

2015-06-30T01:59:02Z

decided that this should point to other Atoms rather than directly to Text

← Older revision		Revision as of 01:59, 30 June 2015
Line 1:		Line 1:
	==About==		==About==
	* '''Purpose''': ~~an atom with~~ a ~~little bit of~~ content ~~and possibly~~ an owner		* '''Purpose''': content type -- has a title and content; optionally, an owner and summary
	* '''Fields''':		* '''Fields''':
	** '''ID_Owner''': ID of user who owns this post (NULL means ownership is not relevant)		** '''ID_Owner''': ID of user who owns this post (NULL means ownership is not relevant)
	*** Some post types will not have owners, but it's a common enough thing that I thought it should go in at a low level.		*** Some post types will not have owners, but it's a common enough thing that I thought it should go in at a low level.
	** '''ID_Title''': ID of {{l/same\|~~text~~}} for title for page headers and narrower listings		** '''ID_Title''': ID of {{l/same\|atom}} for title for page headers and narrower listings
	** '''ID_Summary''': ID of {{l/same\|~~text~~}} for one-line description for wide listings, intro paragraph for blog posts, etc.		** '''ID_Summary''': ID of {{l/same\|atom}} for one-line description for wide listings, intro paragraph for blog posts, etc.
	** '''ID_Body''': ID of {{l/same\|~~text~~}} for main content		** '''ID_Body''': ID of {{l/same\|atom}} for main content
	* '''History''':		* '''History''':
	** '''2013-03-12''' Created, but not yet in use.		** '''2013-03-12''' Created, but not yet in use.
Line 21:		Line 21:
	`ID_Atom` INT NOT NULL COMMENT "ID of atom this post is using",		`ID_Atom` INT NOT NULL COMMENT "ID of atom this post is using",
	`ID_Owner` INT DEFAULT NULL COMMENT "ID of user who owns this post (optional)",		`ID_Owner` INT DEFAULT NULL COMMENT "ID of user who owns this post (optional)",
	`ID_Title` INT NOT NULL COMMENT "ID of ~~text record~~ for title",		`ID_Title` INT NOT NULL COMMENT "ID of atom for title",
	`ID_Summary` INT DEFAULT NULL COMMENT "ID of ~~text record~~ for summary (optional)",		`ID_Summary` INT DEFAULT NULL COMMENT "ID of atom for summary (optional)",
	`ID_Body` INT NOT NULL COMMENT "ID of ~~text record~~ for body of post",		`ID_Body` INT NOT NULL COMMENT "ID of atom for body of post",
	PRIMARY KEY(`ID_Atom`)		PRIMARY KEY(`ID_Atom`)
	)		)

Woozle: text content goes in a separate table

2015-06-29T22:41:50Z

text content goes in a separate table

← Older revision		Revision as of 22:41, 29 June 2015
Line 3:		Line 3:
	* '''Fields''':		* '''Fields''':
	** '''ID_Owner''': ID of user who owns this post (NULL means ownership is not relevant)		** '''ID_Owner''': ID of user who owns this post (NULL means ownership is not relevant)
	** '''Summary''': subject, title, or one-line description
	*** Some post types will not have owners, but it's a common enough thing that I thought it should go in at a low level.		*** Some post types will not have owners, but it's a common enough thing that I thought it should go in at a low level.
			** '''ID_Title''': ID of {{l/same\|text}} for title for page headers and narrower listings
			** '''ID_Summary''': ID of {{l/same\|text}} for one-line description for wide listings, intro paragraph for blog posts, etc.
			** '''ID_Body''': ID of {{l/same\|text}} for main content
	* '''History''':		* '''History''':
	** '''2013-03-12''' Created, but not yet in use.		** '''2013-03-12''' Created, but not yet in use.
Line 13:		Line 15:
	*** Added '''Body''' field to make this independent of the containing [[content management system\|CMS]].		*** Added '''Body''' field to make this independent of the containing [[content management system\|CMS]].
	** '''2013-07-21''' ID_Owner needs to be DEFAULT NULL (not NOT NULL) if it's going to be optional. Duh.		** '''2013-07-21''' ID_Owner needs to be DEFAULT NULL (not NOT NULL) if it's going to be optional. Duh.
			** '''2015-06-29''' Decided that editable text content should be in a separate table, to make it easier to track revisions
	==SQL==		==SQL==
	<mysql>		<mysql>
	CREATE TABLE `~~post~~` (		CREATE TABLE `pf_post` (
	`ID_Atom` INT NOT NULL COMMENT "ID of atom this post is using",		`ID_Atom` INT NOT NULL COMMENT "ID of atom this post is using",
	`ID_Owner` INT DEFAULT NULL COMMENT "~~optional:~~ ID of user who owns this post",		`ID_Owner` INT DEFAULT NULL COMMENT "ID of user who owns this post (optional)",
	`~~Summary~~` ~~VARCHAR(255)~~ NOT NULL COMMENT "~~short description,~~ for ~~listings~~",		`ID_Title` INT NOT NULL COMMENT "ID of text record for title",
	`~~Body~~` ~~TEXT~~ DEFAULT NULL COMMENT "~~body~~ of ~~post~~ (optional)",		`ID_Summary` INT DEFAULT NULL COMMENT "ID of text record for summary (optional)",
			`ID_Body` INT NOT NULL COMMENT "ID of text record for body of post",
	PRIMARY KEY(`ID_Atom`)		PRIMARY KEY(`ID_Atom`)
	)		)

Woozle: 8 revisions imported: PostFerret from ICMS

2015-06-29T01:51:39Z

8 revisions imported: PostFerret from ICMS

← Older revision	Revision as of 01:51, 29 June 2015
(No difference)

Woozle: made ID_Owner DEFAULT NULL

2013-07-24T19:56:46Z

made ID_Owner DEFAULT NULL

← Older revision		Revision as of 19:56, 24 July 2013
Line 2:		Line 2:
	* '''Purpose''': an atom with a little bit of content and possibly an owner		* '''Purpose''': an atom with a little bit of content and possibly an owner
	* '''Fields''':		* '''Fields''':
	** '''ID_Owner''': ID of user who owns this post		** '''ID_Owner''': ID of user who owns this post (NULL means ownership is not relevant)
			** '''Summary''': subject, title, or one-line description
	*** Some post types will not have owners, but it's a common enough thing that I thought it should go in at a low level.		*** Some post types will not have owners, but it's a common enough thing that I thought it should go in at a low level.
	* '''History''':		* '''History''':
Line 11:		Line 12:
	*** Removed owner/summary uniqueness requirement; can't see need for this either (e.g. multiple posts might be called "status report", for example).		*** Removed owner/summary uniqueness requirement; can't see need for this either (e.g. multiple posts might be called "status report", for example).
	*** Added '''Body''' field to make this independent of the containing [[content management system\|CMS]].		*** Added '''Body''' field to make this independent of the containing [[content management system\|CMS]].
			** '''2013-07-21''' ID_Owner needs to be DEFAULT NULL (not NOT NULL) if it's going to be optional. Duh.
	==SQL==		==SQL==
	<mysql>		<mysql>
	CREATE TABLE `post` (		CREATE TABLE `post` (
	`ID_Atom` INT NOT NULL COMMENT "ID of atom this post is using",		`ID_Atom` INT NOT NULL COMMENT "ID of atom this post is using",
	`ID_Owner` INT ~~NOT~~ NULL COMMENT "optional: ID of user who owns this post",		`ID_Owner` INT DEFAULT NULL COMMENT "optional: ID of user who owns this post",
	`Summary` VARCHAR(255) NOT NULL COMMENT "short description, for listings",		`Summary` VARCHAR(255) NOT NULL COMMENT "short description, for listings",
	`Body` TEXT DEFAULT NULL COMMENT "body of post (optional)",		`Body` TEXT DEFAULT NULL COMMENT "body of post (optional)",
	PRIMARY KEY(`ID_Atom`)		PRIMARY KEY(`ID_Atom`)
	)		)

Woozle: syntax fix

2013-07-14T16:40:44Z

syntax fix

← Older revision		Revision as of 16:40, 14 July 2013
Line 18:		Line 18:
	`Summary` VARCHAR(255) NOT NULL COMMENT "short description, for listings",		`Summary` VARCHAR(255) NOT NULL COMMENT "short description, for listings",
	`Body` TEXT DEFAULT NULL COMMENT "body of post (optional)",		`Body` TEXT DEFAULT NULL COMMENT "body of post (optional)",
	PRIMARY KEY(`ID_Atom`),		PRIMARY KEY(`ID_Atom`)
	)		)
	ENGINE = MYISAM;		ENGINE = MYISAM;

Woozle: revisions

2013-06-28T21:37:06Z

revisions

← Older revision		Revision as of 21:37, 28 June 2013
Line 2:		Line 2:
	* '''Purpose''': an atom with a little bit of content and possibly an owner		* '''Purpose''': an atom with a little bit of content and possibly an owner
	* '''Fields''':		* '''Fields''':
	** '''ID_Owner''': ID of user who owns this ~~atom.~~		** '''ID_Owner''': ID of user who owns this post
	*** Some post types will not have owners, but ~~this needs to be here so~~ it ~~can be part of the unique key. We don~~'~~t want to prevent different users from using the same Summary.~~		*** Some post types will not have owners, but it's a common enough thing that I thought it should go in at a low level.
	** '''URI''': I ~~haven't yet decided if this really belongs here or how to formally define it, but~~ it ~~could be used for either:~~
	~~***~~ a ~~page on the site which is set aside for more information about the given post~~
	*** the post's official URI on the site
	* '''History''':		* '''History''':
	** '''2013-03-12''' Created, but not yet in use.		** '''2013-03-12''' Created, but not yet in use.
	** '''2013-03-15''' Most fields moved from {{l/same\|post}} to {{l/same\|atom}}; added ID_Owner.		** '''2013-03-15''' Most fields moved from {{l/same\|post}} to {{l/same\|atom}}; added ID_Owner.
			** '''2013-06-28'''
			*** Decided to remove '''URI''' until there's a clear purpose and need for it.
			*** Removed owner/summary uniqueness requirement; can't see need for this either (e.g. multiple posts might be called "status report", for example).
			*** Added '''Body''' field to make this independent of the containing [[content management system\|CMS]].
	==SQL==		==SQL==
	<mysql>		<mysql>
	CREATE TABLE `post` (		CREATE TABLE `post` (
	`ID_Atom` INT NOT NULL COMMENT "ID of atom this ~~sign~~ is using",		`ID_Atom` INT NOT NULL COMMENT "ID of atom this post is using",
	`ID_Owner` INT NOT NULL COMMENT "optional: ID of user who owns this ~~sign~~",		`ID_Owner` INT NOT NULL COMMENT "optional: ID of user who owns this post",
	`Summary` VARCHAR(255) NOT NULL COMMENT "short description, for listings",		`Summary` VARCHAR(255) NOT NULL COMMENT "short description, for listings",
	`~~URI~~` ~~VARCHAR(255)~~ DEFAULT NULL COMMENT "optional ~~site-relative URI for more information~~",		`Body` TEXT DEFAULT NULL COMMENT "body of post (optional)",
	PRIMARY KEY(`ID_Atom`),		PRIMARY KEY(`ID_Atom`),
	~~UNIQUE KEY `content` (`ID_Owner`,`Summary`)~~
	)		)
	ENGINE = MYISAM;		ENGINE = MYISAM;
	</mysql>		</mysql>
			==Obsolete==
			* '''URI''': I haven't yet decided if this really belongs here or how to formally define it, but it could be used for either:
			** a page on the site which is set aside for more information about the given post
			** the post's official URI on the site
			<mysql> `URI` VARCHAR(255) DEFAULT NULL COMMENT "optional site-relative URI for more information",</mysql>

Woozle: corrected table name in CREATE

2013-03-17T17:52:53Z

corrected table name in CREATE

← Older revision		Revision as of 17:52, 17 March 2013
Line 1:		Line 1:
	==About==		==About==
	* '''Purpose''': an atom with a little bit of content and possibly an owner		* '''Purpose''': an atom with a little bit of content and possibly an owner
			* '''Fields''':
	** '''ID_Owner''': ID of user who owns this atom.		** '''ID_Owner''': ID of user who owns this atom.
	*** Some post types will not have owners, but this needs to be here so it can be part of the unique key. We don't want to prevent different users from using the same Summary.		*** Some post types will not have owners, but this needs to be here so it can be part of the unique key. We don't want to prevent different users from using the same Summary.
	* '''Fields''':
	** '''URI''': I haven't yet decided if this really belongs here or how to formally define it, but it could be used for either:		** '''URI''': I haven't yet decided if this really belongs here or how to formally define it, but it could be used for either:
	*** a page on the site which is set aside for more information about the given post		*** a page on the site which is set aside for more information about the given post
Line 12:		Line 12:
	==SQL==		==SQL==
	<mysql>		<mysql>
	CREATE TABLE `~~sign~~` (		CREATE TABLE `post` (
	`ID_Atom` INT NOT NULL COMMENT "ID of atom this sign is using",		`ID_Atom` INT NOT NULL COMMENT "ID of atom this sign is using",
	`ID_Owner` INT NOT NULL COMMENT "optional: ID of user who owns this sign",		`ID_Owner` INT NOT NULL COMMENT "optional: ID of user who owns this sign",

Woozle: tweaks

2013-03-16T01:12:18Z

tweaks

← Older revision		Revision as of 01:12, 16 March 2013
Line 2:		Line 2:
	* '''Purpose''': an atom with a little bit of content and possibly an owner		* '''Purpose''': an atom with a little bit of content and possibly an owner
	** '''ID_Owner''': ID of user who owns this atom.		** '''ID_Owner''': ID of user who owns this atom.
	*** Some ~~sign~~ types will not have owners, but this needs to be here so it can be part of the unique key. We don't want to prevent different users from using the same Summary.		*** Some post types will not have owners, but this needs to be here so it can be part of the unique key. We don't want to prevent different users from using the same Summary.
	* '''Fields''':		* '''Fields''':
	** '''URI''': I haven't yet decided if this really belongs here, but it could be used for either:		** '''URI''': I haven't yet decided if this really belongs here or how to formally define it, but it could be used for either:
	*** a page on the site which is set aside for more information about the given post		*** a page on the site which is set aside for more information about the given post
	*** the post's official URI on the site		*** the post's official URI on the site

Woozle at 20:49, 15 March 2013

2013-03-15T20:49:54Z

← Older revision		Revision as of 20:49, 15 March 2013
Line 1:		Line 1:
	==About==		==About==
	* '''Purpose''': a ~~trackable piece~~ of ~~text (~~can be ~~modified~~, ~~has edit history, etc.)~~		* '''Purpose''': an atom with a little bit of content and possibly an owner
			** '''ID_Owner''': ID of user who owns this atom.
			*** Some sign types will not have owners, but this needs to be here so it can be part of the unique key. We don't want to prevent different users from using the same Summary.
			* '''Fields''':
			** '''URI''': I haven't yet decided if this really belongs here, but it could be used for either:
			*** a page on the site which is set aside for more information about the given post
			*** the post's official URI on the site
	* '''History''':		* '''History''':
	** '''2013-03-12''' Created, but not yet in use.		** '''2013-03-12''' Created, but not yet in use.
	* '''Fields''':		** '''2013-03-15''' Most fields moved from {{l/same\|post}} to {{l/same\|atom}}; added ID_Owner.
	** '''~~URI'~~''~~: I haven~~'~~t yet decided if this really belongs here, but it could be used for either:~~
	*** - a page on the site which is set aside for more information about the given post
	*** - the post~~'s official URI on the site~~
	==SQL==		==SQL==
	<mysql>		<mysql>
	CREATE TABLE `~~post~~` (		CREATE TABLE `sign` (
	`ID` INT NOT NULL ~~AUTO_INCREMENT~~,		`ID_Atom` INT NOT NULL COMMENT "ID of atom this sign is using",
	`Summary` VARCHAR(255) NOT NULL COMMENT "short description ~~of post~~, for listings",		`ID_Owner` INT NOT NULL COMMENT "optional: ID of user who owns this sign",
	`URI` VARCHAR(255) DEFAULT NULL COMMENT "site-relative URI for more information",		`Summary` VARCHAR(255) NOT NULL COMMENT "short description, for listings",
	~~`WhenCreated` DATETIME NOT NULL COMMENT "when this question was entered",~~		`URI` VARCHAR(255) DEFAULT NULL COMMENT "optional site-relative URI for more information",
	~~`WhoCreated` INT NOT NULL COMMENT "ID (site-defined) of user who added the question",~~		PRIMARY KEY(`ID_Atom`),
	~~`WhenEdited` DATETIME DEFAULT NULL COMMENT "when this question was last edited",~~		UNIQUE KEY `content` (`ID_Owner`,`Summary`)
	~~`WhoEdited` INT DEFAULT NULL COMMENT "ID of user who last edited the question",~~
	~~`QtyEdits` INT DEFAULT NULL COMMENT "number of times this question has been edited~~",
	PRIMARY KEY(`ID`),
	UNIQUE KEY `content` (`Summary`)
	)		)
	ENGINE = MYISAM;		ENGINE = MYISAM;
	</mysql>		</mysql>

Woozle: Woozle moved page PostFerret/sql to PostFerret/sql/post without leaving a redirect: ...duhhh...

2013-03-15T18:06:11Z

Woozle moved page PostFerret/sql to PostFerret/sql/post without leaving a redirect: ...duhhh...

← Older revision	Revision as of 18:06, 15 March 2013
(No difference)