Re: [mbackup-devel] indexing brainstorm and sqlite

[James O'K. <jo...@mi...>]

Since a few people emailed me privately with similar comments, I'll reply
to the group. 

I'm looking for brainstorm help to get an idea of the various things that 
people might want to query for, so that I can define the API for index 
modules. Since sql the language would be an implimentation detail, I don't 
want to have sql statements outside of the index module. That way, if 
someone wants to finish work on the db3 stuff, they don't have to 
impliment the sql language.

Right now, I have 
mb_index::insert(mb_index_entry)
mb_index::lookup(string filename)

I could keep adding functions like lookup_directory_contents() and 
lookup_backup_set() and others, but I'm hoping to come up with a more 
generic interface.

At the moment, I've been considering changing things to
insert(mb_index_entry)
lookup_exact(mb_index_entry)
lookup_children(mb_index_entry)

And you set the parts of mb_index_entry as appropriate, but I don't think 
that will work well.

-james