Monday, January 16, 2012

Happenings in semantic engine

Lurker that I am. Last time we checked, the issue was how do BSON streams ever get connected up in a flexible storage system with B-Tree. It looks like the InnoDB B-Tree system is winning the game. Not yet a slam dunk, but lurking around and watching the No-SQL vendors try to dump SQL, they realize the baby-bathwater thing, dump SQL if it helps, but keep the B-Tree. Oracle owns InnoDB (B-Tree system) , last I heard, but there is a GNU license, which MySql has made use of. InnoDB supports MySql.

MongoDB changed their name, or rather I did, I preferred to call them the fruit company. They are going to be fun to watch, they are making an attempt at JSON query syntax, and dealing with confusion about which objects needs quotes and which don't. There system abounds in quote characters. They also struggle with the $ punctuation mark, when it is used and when it is not. Eventually there is gonna be a pow wow concerning the correct form of JSON as a query by example, otherwise known as mobile graphs.

I have no idea why the No-SQL crowd limited themselves to name/value pairs, the market has already selected the <subject,predicate,object> format.
Then there is the BerkeleyDB storage engine, look to have the hooks.  Looking at it now. But, I still an favoring sqlite, sql and all.  With sql we get a microcode that supports the semantic layer. What is wrong with that?

No comments: