Okay, let's take a few minutes to learn about the heart of Frontier: the Object Database.
Sometime people freeze up when they hear "Object Database". It sure sounds imposing, like object-oriented programming or something like that. Well, it's not difficult at all, as you'll soon see. In fact, once you get used to working in Frontier's database, you'll hardly even notice that it's there.
Ready? Let's go!
It's a file, just a file.
The database is a file that is shipped along with the Frontier application. The database is called "Frontier.root", and looks like this:
Looks small, doesn't it? Frontier's database is like a genie's bottle-- it's bigger inside than it is outside--and there are all kinds of magical things inside. Well, not quite magical, but it's amazingly useful.
It's just a file, very similar to the word processing files and spreadsheets you've worked with before. One important similarity it has with all other data files: it should be backed up regularly. More on that later, but the main point here is that it's similar to what you've worked with in the past.
There are a few differences. Frontier's database can hold all kinds of data--and there's no apparent size limit. The size of the database file is only limited by memory and hard disk space. Some people feel a little uncomfortable when their Frontier database grows past 10 megabytes or so; but this is not uncommon. My database runs around 20 megabytes (I use it heavily) and files upwards of 50 or 60 megabytes are not unheard of. The Frontier database, as it ships, starts at about 3 megabytes.
It's a hierarchical, persistent, object database.
Yow. Some jargon here. But let's take it a bit at a time, starting from the end.
An object database. If you've ever used a database like Filemaker or Access, you're familiar with the idea of fields and records. A record is like a rolodex card, and the fields are the individual bits of data on the card: name, address, phone number.
Frontier's database isn't like that. I like to think of it as a closet, or pantry. My closet holds all kinds of different items, and I arrange them in a way that is meaningful to me. Books about Miles Davis don't go with my children's book collection. I may have a box of photos and t-shirts. They go together because it's stuff from my high school days.
Frontier keeps all kinds of different data--and it's arranged loosely on type, purpose, or usage... depending on which ever organization makes the most sense. So it's a very flexible and powerful data storage system.
By the way, we often abbreviate object database as ODB.
It's a persistent database. Data stored in Frontier stays there, in the same place, and is always available.
With some scripting languages, the information being processed only exists for the life of the program. Once the script stops running, the data disappears. Other scripts can't get to that information.
It's the difference between backpacking, and setting up house. When you backpack, you can really get around, but you're constantly expending energy on finding a place to sleep, a place to send and pick up mail. When you've got a house, you can spread out, and leave work for later--even go on a trip for a while. All your stuff (even dirty laundry) will be there for you when you get back.
This is an important point. Frontier's database is the environment for you to get work done. It's a workshop for your productivity.
It's a hierarchy Since Frontier doesn't use the index card style of most databases, it structures its data in a tree. The top level of the tree is called the root. Everything in the database is kept stored in branches (in Frontier, called tables) of this tree. And branches can have sub branches (tables have subtables) and so on.
Whew! We made it through the jargon. What does all this stuff mean? It means that Frontier's database offers real advantages for getting work done!
Page 1: Frontier's Database Defined
Page 2: The Advantages of Frontier's Database
Page 3: What's in the root?
Page 4: Navigating the Root
Page 5: Where do I keep my stuff?
Page 6: Database Names and Addresses
Page 7: Database Care and Feeding
Page 8: Object Database Tech Notes
News
