Dealing with table names

Table names are a key word, like any other. Internally they are a link, and changing tables opens the doors of how searches are transparently linked across tables, databases and locations. Ultimately, the urls,names, database names, and all the links are just keywords with special attributes. So we have to have attributes.

I thin we should pick the most hideous of punctuation marks for the cause, but let's ot tell the client about it, he fears typeface explosion. Internally, then, all key words are the same, and G takes the syntax ad starts it normal matching with the default, local entry point. Should it match on table name, the first key word in the syntax, the it can get the attributes.

What attributes does G know about? It knows an sql TABLE, and sqlite3 TEXT or INT, and it knows SQUARE as an overload attribute on table. So the attribute link binds to its key word, it cannot be floated with the parenthesis.

FarTable.k1, then FarTable gets the first match, and linking kicks in when the attribute is TABLE, and not this current table. This is current industry practices, nothing new. It just means that my little gadget will await a version or two, and table swaps are going to be hokey for a while, and local. Also there is the issue of how sqlite3 standard practices are today, I think network file system. Bottom line, a kludge will do for now.