@Aki Couple of things. I was very careful to point out that the database is an InProc database. Which essentially means it will be a DLL you include in your app. Therefore issues of ports, updates, etc does not arise. As for converting data for many years I have and will continue to insist that data be stored in its correct type. This costs nothing and has innumerable benefits. As for limits I cannot speak for SQLite but for SQL Compact the max size is 4Gb and it is threadsafe, so lots of frequent writes will not be a problem. Parsing a 4GB text file, even if using a fast XML parser, however will take you a LOONG time. On Wed, Feb 29, 2012 at 11:49 AM, aki <aki275@gmail.com> wrote:
@Rad, @Martin. Thnks for the suggestions and good reading too. Will take a look. :-)
Am avoiding to use any DB'es primarily because of security concerns of leaving ports open to run queries, ensuring all the updates/patches are always there, and also having to convert data to e.g. strings and back to avoid sql injections. I'm also visualising a situation where the use of Lite databases will run into limits problems as the data inputs could reach an update every second, thus within 1 year or so, the limit threshold will have been reached.
Besides what you have already suggested, any other suggestion that I can work at pure file level would be much appreciated.
Cheers. :-)
_______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke