They are an index. Value can be unnamed, their location known locally relative to their enclosing predicate. So that means the engine, ultimately has to make sure names are indexed? Well, yes, it the intent is intelligent storage in the local data base. What gets me learning, actually, I haven' gotten as far as indexing. But, just scan the store for indexed names, and put the rowid,name,table in the local named index graph? I could spend a few days and write a good enough sql indexing set up, assign it to an operator, then run the operator after a table load. Then show it to a CIO control freak an make a gazillion dollars.
How would I manage indices using type face explosion? Dunno, right now I only know aout two graps in convolution generating a result graph. I think the TE variable and insert graph routines need to wait until the Json crew thinks a bit about Json as a query by example.
But, I can sure do it in SQL, I can make the index table:
|name|table|rowid|,
good for any database of Bson stores, and its not even in triple form!. I would index on name, then look up location by name. I could actually execute a new insert name into index operator any time I want, any time I need to, fast, I have the operator all set up, precompiled.
This is the stuff you can do with the engine.
No comments:
Post a Comment