• entries
    437
  • comments
    1000
  • views
    335623

Query interface

Sign in to follow this  
evolutional

63 views

I'm chipping away at the basic query interface now; I'll probably be working on a working implementation of it tomorrow. The main thing right now is to ensure the interfaces are usable before I try to throw an implementation at it.

I've been pondering a potentially sticky issue that will be of crucial importance when I decide to move out of the prototype stage and into a real-working version. The prototype doesn't care much for speed, so I can can 'query' quite easy by iterating the atributes of all my objects. As you can imagine, scale this up a hundred (or eve a thousand) fold and we're starting to think of real number to work with. Instead of storing copies of the attributes in the objects, I'm going to need to have a way of typing things together to ensure things such as indexes are updated. The best way I see so far is to have multiple indexes stored within the database and the database itself being effectively a 'pot' of attributes with a reference to the object it belongs to. Likewise, the objects need to maintain references to the attributes they hold.

I'll work on this problem later, but must bear it in mind at this prototype stage as it will likely affect my interfaces and how the objects link together.
Sign in to follow this  


0 Comments


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now