Comments on: SQLite for C# – Part 2 – How do I setup a SQLite DB (without coding) http://www.csharphacker.com/technicalblog/index.php/2009/06/17/sqlite-for-c-part-2-how-do-i-setup-a-sqlite-db-without-coding/ Thoughts and ponderings on the technical world Fri, 06 Aug 2010 03:40:04 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Gareth http://www.csharphacker.com/technicalblog/index.php/2009/06/17/sqlite-for-c-part-2-how-do-i-setup-a-sqlite-db-without-coding/comment-page-1/#comment-86 Gareth Tue, 25 Aug 2009 00:49:03 +0000 http://www.csharphacker.com/technicalblog/?p=182#comment-86 Sorry for the slowness for this to appear in the site, it got eaten! Secondarily I'm glad it helped! As for the question I intentionally coded the path into it as it becomes apparent that we are really talking about a file. As for its location I would strongly recommend keeping the database with your application, or a subfolder beneath your application root. I would definitely not hard code it to be anything specific if you intend to be portable! The sizing shouldnt matter as the database manages its own size, but you will likely need to vacuum the file periodically. Hope this helps some, Gareth Sorry for the slowness for this to appear in the site, it got eaten! Secondarily I’m glad it helped!

As for the question I intentionally coded the path into it as it becomes apparent that we are really talking about a file. As for its location I would strongly recommend keeping the database with your application, or a subfolder beneath your application root. I would definitely not hard code it to be anything specific if you intend to be portable! The sizing shouldnt matter as the database manages its own size, but you will likely need to vacuum the file periodically.

Hope this helps some,

Gareth

]]> By: John Balderston http://www.csharphacker.com/technicalblog/index.php/2009/06/17/sqlite-for-c-part-2-how-do-i-setup-a-sqlite-db-without-coding/comment-page-1/#comment-81 John Balderston Wed, 19 Aug 2009 19:57:49 +0000 http://www.csharphacker.com/technicalblog/?p=182#comment-81 First I want to say Thank You. This was the first tutorial that explained this subject that I have been able to find. Now my question. In the Add Connection dialog, the entry, "C:/CSharpCoderSample.db3" looks like a path to a file in the root directory. I understand that it is actually the name of the db connection. What I want to know is, where is a good place to put the actual SQLite db name CSharpCoderSample? I discovered that CSharpCoderSample.db3 is actually a file in the root (C:\) directory. Might it not be better to create a subdirectory like C:\SqLiteDbs, and locate the CSharpSampleCoder.db3 there. What are the pros and cons of this? And what is the optimal way tp do this if I plan to have several dbs of varying size? First I want to say Thank You. This was the first tutorial that explained this subject that I have been able to find.

Now my question. In the Add Connection dialog, the entry, “C:/CSharpCoderSample.db3″ looks like a path to a file in the root directory. I understand that it is actually the name of the db connection. What I want to know is, where is a good place to put the actual SQLite db name CSharpCoderSample? I discovered that CSharpCoderSample.db3 is actually a file in the root (C:\) directory. Might it not be better to create a subdirectory like C:\SqLiteDbs, and locate the CSharpSampleCoder.db3 there. What are the pros and cons of this? And what is the optimal way tp do this if I plan to have several dbs of varying size?

]]>