On 5/22/2010 12:56 AM, Chris Nystrom wrote: > Below is an example c program that I wrote to use the SQLite library > (http://www.sqlite.org/). It compiles without error under Linux. > > SQLite seems to be far more trouble to use than simply creating > arrays. I assume that as you scale up though, it is important for > performance to have an actual database instead of internal arrays of > data. Is there a rule of thumb about when you should use a database? > Or is there some other reason to use SQL besides performance with > large systems? SQL databases don't exist for performance. In addition to what Alan mentions, databases are good for maintaining data integrity in the face of complex relations, and of course doing analysis on it while it's in use (and analyzing it in ways you didn't know you wanted to... SQL is great for ad-hoc analysis). -- Matthew Weigel hacker unique & idempot . ent --------------------- To unsubscribe go to http://gameprogrammer.com/mailinglist.html