Changing bases is fundamental to computer science because bits are binary. For example, programmer who work close to the CPU level would work with numbers and code in octal (base 8) or hexadecimal (base 16) becasue those bases work well with binary (base 2)
A in base 12 would mean the same value as 10 in base 10. B in base 12 would mean the same thing as 11 in base 10. and 10 in base 12 means you have one complete set of 12 so you move over tot he next digit place and put a 1 there making it 10 base 12.
A relational database design uses an entity (table) for each logical groupings of tuples (rows: people, places, things). It follows then that each foreign key relationship between tables is a specific foreign key. For example, a relational database with about 50 tables might have 50 different foreign keys.
So the answer to, Why a Graph Database? is that TejonDB is designed to be highly configurable and flexible, and the graph database design is extremely flexible - much more so than the traditional relational database. (as a side note, I designed the initial pattern for generalized connections while experimenting with sentence structures for data, several years before I heard the term graph database. The pattern is just that intriguing.)
TejonDB takes it a step further by adding object-oriented structure and usage rules to which classes (types) and statuses (statuses), because just adding a label to a node or connection is too slippery for enterprise use.
I'm a science fiction geek and I admit I liked Timeline - the book by Michael Crichton and the 2003 movie. Give me adventure, swords, a little romance, and some time travel and I'm hooked. Which is a problem for relational databases.
TejonDB takes the basic concepts of data auditing and modeling historical data and pushes it to the next level. To visualize the temporal data, TejonDB sports a graphical timeline of the object's type / status and region history. What's more, every Filter Element can search for current data, data at any time in the history of the object, or data for a specific date range. For us, data history is just a audit trail, deep in the database engine, TejonDB is a temporal (timeline) database.
Why did we go to such lengths? Because organizations are about relationships, and relationships are about history.
We chose Tejon Technologies for our company name for several great reasons:
Tejon Technologies is located in Epicentral - the coolest co-working place in the Springs at 415 N. Tejon St., and our servers are located down the street at Data102, named for it's location at 102 S. Tejon St.
Acacia Park, right on Tejon Street is like Central Park for Colorado Springs.
General William Palmer planned the city streets of Colorado Springs. The north-south streets (including Tejon Street) are named for battles and locations were he fought in the US Civil War in the 1860's. The east-west Streets are named for rivers (mountains?) that he conquered.