No, that's ok :) We are pretty much stuck with SQL as the application itself holds various data - the tree is just one small representation of a subset of information that we store.
> -----Original Message----- > From: Martin Jenkins [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 27, 2007 8:59 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Questions on views > > Dennis Volodomanov wrote: > > > [...] > > The reason that such a huge amount of statements needs to > be executed > > so many times very quickly is that we have a tree built up based on > > those statements and that tree needs to be pruned if the results of > > statements are empty in real-time as the user is typing a string (a > > search string basically). > > [...] > > Sorry to butt in (especially without knowing your > constraints) but is SQL the right approach to use here? Isn't > this the sort of thing that Patricia/radix/suffix trees are used for? > > NB: I've just got up and haven't had any tea to start the > boot process yet, so I could be talking (more) nonsense (than > usual). ;) > > Martin > > -------------------------------------------------------------- > --------------- > To unsubscribe, send email to [EMAIL PROTECTED] > -------------------------------------------------------------- > --------------- > > ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
