Wednesday, January 07, 2015

Yes, SQL can be helpful to novelists and screenwriters

In setting up the worksheets for my major screenplay and novel, I’m going to keep track of “loose ends” in Microsoft Access.

There are incidents that are common to both the screenplay and the novel.  What would be of interest is to match the characters involved, when the incidents are supposed to have occurred, and the relationship of the incident to the particular character’s sense of reality.

For example, a “reality code” could be set up as follows, with respect to up to two characters: the subject, and the “remote viewer”

1000 – present day reality
2000  -  flashback for something that actually happened, by direct narrative
2100  -  flashback detected from online writings of subject (2110 is deep web only; 2120 is searchable web only, 2130 is whitelisted only; 2140 is Internet Archive)
2200  -  flashback detected from books by subject (positional within code)
2300  -- flashback detected from government wiretap (legal or illegal)
2400  -  flashback hacked from subject’s computer
2500  -  flashback hacked by telepathy
2600  -- flashback hacked by advanced remote viewing (as at Monroe Institute)
3000  -- fictive (with subcodes to show detection by viewer as with flashback)

a suffix "01" means it is supplemented by the subject's verbal narrative. An "09" means that some aspect of narrative is deliberately blocked from some remote viewers. 
A flashback could be further characterized by another field showing the name of any other manuscript (of mine or of “Bill’s”, or any other character) in which the same incident had been reported.

It will be possible to keep track of characters in a table that lists the physical characteristics, DOB, personality traits, master name, and possibly real life identity (that is dangerous – hence the “encypted” master name).  Then the same character can have other names in different screenplays and novels but would need a “master name” entry.  If the same character can have different names in different works, the character table would need to add “alias” master names.

Microsoft has a pretty good writeup of the SQL for its own Access products here.  Notice that in Inner Joins and Outer Joins, you don’t to have the field names in different tables match, but the values need to (hence alias fields for characters).  For Unions, you would need field names to match. The Access SQL seems to be a subset of the ANSI standard or what you would get with MySQL or DB2 (which is slightly different). 
As work on my manuscripts progresses this month, I’ll post more details on my Wordpress media blog. 

No comments: