The issue sort of evaporates. Fro the point of view of Sqlite3, it simply means they compete with the table system for naming sequences of Bson, they offer high powered rowid indexing, and subgraph indexing.
The storage standard has become Bson serial, one way or the other anyway. Sqlite keeps its opcode system for a while, but Bson sequences can easily exchange with them. Sqlite can go into the B Tree and set fom page partitions values, optimized for typical triple storage. Sql syntax becomes a variation of a Bson named call. I think sqlite3 still wins the game here, with BerkeleyDB coming in second. But someone will produce the open source version of B-Tree optimizable, that is easily adjusted in page partitions for various types of storage.
Then, my 1500 lines of semantic machine is translated into Javascript, and each browser becomes a Watson in the semantic ocean
0 comments:
Post a Comment