I need an SQL engine, which is based on files instead of a background process like mysql.
Ideas?
Basically I need to use a database mechanism, even if I have no mysql process running.
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
July 29, 2011 7:19am
Subscribe [2]#1 / Jul 29, 2011 7:19am
I need an SQL engine, which is based on files instead of a background process like mysql.
Ideas?
Basically I need to use a database mechanism, even if I have no mysql process running.
#2 / Jul 29, 2011 10:46am
CSV? SQLite?
#3 / Jul 29, 2011 11:28am
I’ve read about sqlite, but how reliable is it? I want to use it with CI
The doc says: it’s one big file. What if someone finds the path to my DB file?
#4 / Jul 29, 2011 11:35am
Keep it out your Webserver root… Only your index.php should be exposed to the outside.
#5 / Jul 29, 2011 11:36am
/var/www/sqlite.db
/var/www/site.com/... right?
#6 / Jul 29, 2011 11:47am
we usually have this structure:
/somedir
/application
/codeigniter
/db (in case of sqlite)
/public_html
index.php#7 / Jul 29, 2011 11:52am
Damn, I forgot. It’s been almost 6 months since I didn’t work with CI. at that time I have a linux VM, where I managed to setup this, and it worked.
Thanks for reminding me
#8 / Jul 29, 2011 6:01pm
Is there any good SQLite integration tutorial? I didn’t find one
#9 / Jul 31, 2011 1:55am
but how will sqlite or any other file based db support hudreds of clients? Can it be used on a busy site?
#10 / Aug 05, 2011 5:34am
It can but why would you want that?
If the site is busy use a real DB. It’s what they are for…