There are many important variables to consider.  What kind of data?  How
many tables (if a relational DB approach even makes sense)? How many
records in each table?  How will this data be queried?  Many different,
often unperdicatable ways? Or just a couple static ways?  

There's nothing faster than having the data in RAM (if you can fit all
your data in what's available that is).  A fast approach might be to
write a C program that stores the data in a static array of a data
structure, sort that array according to what you expect to be querying
on, then use a b-tree search algorithm to query.  I've done this myself
in the past.  It's probably what the relational DB engines do "under the
hood".  

SQLite might be a good solution because it's in-memory, easy to use and,
if constructed right, runs fast.  It can also deal with unpredictable
queries from users.

So, you have to be a lot more specific.

-dave

-----Original Message-----
From: Lloyd [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, April 11, 2007 11:12 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Data structure


> 
> I was just wondering what the odds were of doing a better job than the

> filing system pros, how much time/code that would take on your part
and 
> how much that time would cost versus speccing a bigger/faster machine.
> 
> Martin

I am not fully clear. I just want my program to run at most efficient
and fast even on a low profile end user system. So I am in search for
the best data structure. 

I have heard about bloom filter, but in my case it is not applicable.
The final point is, I am just searching for a data structure which is
the result of lateral thinking by experts ;) (like bloom filter)

Thanks,
  Lloyd


______________________________________
Scanned and protected by Email scanner

------------------------------------------------------------------------
-----
To unsubscribe, send email to [EMAIL PROTECTED]
------------------------------------------------------------------------
-----

-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to