Mid-Month Report in which I talk about JSON

So far, my 2016 has been a success factory!

1. Operation New (to me) Desk remains on target, if not slightly ahead of schedule.
2. My keyboard tray arrived and I assembled and attached it.
3. My file cabinet/printer stand arrived, and I assembled it, put it next to the desk, put the printer on it, and then put stuff in the drawers.
4. I researched, decided, ordered and obtained a new chair. It arrived and I assembled it and I’m now sitting on it.
5. My Demon Warlord is at the proofreader.
6. I got all the files for the stand alone novella release of An Unsuitable Duchess to the person I decided to use for all my formatting going forward.
7. I asked my graphics guy to do color versions of some custom work he did for me because I’ve stopped kidding myself that I want to deal with it myself. Finals arrived today. They’re awesome.
8. I found someone to do the cover for An Unsuitable Duchess and that’s done. I’m just waiting for the final files.
9. I hire someone to do a software update for me because that’s another thing I don’t have time for.
10. Print cover for My Demon Warlord is done and awaiting final page count.

And, here’s a coincidence that I thought was pretty funny, which in a way is No. 11 only it’s not done yet. I was emailing with my formatter who mentioned that he was using JSON files for a database source and I sent him this screenshot:

screenshot of a JSON file. Code.

JSON

Because I was, at at very moment, working out the schema for my planned DB to manage my ebook info and links because I didn’t put it all in something SQL Server-ish because — I do that all day, and I didn’t want to come home and do more even though I could have bothered to learn MySQL and used that but to be honest, a NoSQL solution was way more interesting to me and I even think it’s more appropriate, because NoSQL is kind of designed for systems that are a bit fluid the way this book shit is, and now I don’t have deal with NULLs and spend more time than I want to properly architect the relational version because, quite literally, I would be sitting there going, but how would I scale this out?? if I took shortcuts that denormalized the tables. That would drive me nuts. And so.

I picked one book as my sample schema document and started setting out the data and mapping the arrays and since I have mongoDB installed on the macs I guess I’ll just put it all in MongoDB and now I’ll get my money’s worth from the time I decided to buy my own Mongo GUI tools from when I was playing around with MongoDB at the previous day job and getting SQL Server to produce JSON files for me. Supposedly SQL Server 2016 CTP 3.2.1 (which I have at the current day job)  can supposedly do this without all the shennanigans I went through in SQL 2012. So, fun, eh?

 

 

Share

Tags: ,

Comments are closed.