SQL for Sequels

Mixing my topics today and probably confusing everyone in the process including me.

SQL stands for Structured Query Language a method of querying databases to find results but often used to describe the database itself. It is normally pronounced sequel hence the connection.There are several databases that call themselves SQL including Microsoft’s larger server based system, right down to SQLite Personal Edition running on various operating systems. Why is a SQL database on my mind? Because my sequels are causing me problems.

Part Three of the Demise Conspiracy, An Agent’s Prize, Part Two of The Observer Series, Intervention and an as yet unnamed sequel to To The Survivors currently named TTS2 by file name. What has this to do with databases. Characters that is what. Characters and timelines and scenes. Of course it’s all my own fault for trying to write several books (not just these) at the same time, but now I have added to my problem. Which character appeared, when, in which book, and do I need to explain their role or half the story of the earlier parts.

As I have previously blogged, I use Scrivener to write and it is an excellent system to list characters and scenes within a manuscript. I have tried importing all the characters over from the earlier parts but that just makes the lists longer. What I need is a clever database that tells me when, where and in what context I wrote about the character or the scene. In other words i need to add all the meta-data and link all the appearances of the character in Scrivener. I also need to know how much I should cover of the earlier story in order to have the current actions make sense. Not sure any tool can help with that. Many might say it did not make sense in the first parts!

Currently, I end up re-reading long sections of the earlier books, using Scriveners’ tool set to find the relevant section, but then comes the real problem. I end up wanting to change the original for grammar, construction or even plot to fit in with the next part’s scene. Oh if only I had written it differently, called the character something else, not killed off xx. God knows how longer series writers manage. Did  J K Rowling have a database of Harry Potter characters? Now if I had a database of all my ideas, characters etc there would be one place to go. This would avoid one section I just had to change where I used the same character name in two different manuscripts.

So clever database designers get on it. Get me a SQL database with the right easy to use queries so that I can look it all up. My writing would increase in speed, I could effortlessly cross reference and the world would be a better place.

Of course I could just get better organised get the sequel written without SQL at all.

Advertisements