Rails will create a “development.sqlit3” file if one doesn’t exist -
note that this is not actually a sqlite3 database, just a file with
that name.
Are you building a site that does not use ActiveRecord? If that is the
case, setup your environment to exclude the ActiveRecord framework
(see comments in environment.rb).
If it is a version control issue, i.e.not wanting to include sqlite3
files in your repository, then ignore the files (.gitignore if using
git)
Rails will create a “development.sqlit3” file if one doesn’t exist -
note that this is not actually a sqlite3 database, just a file with
that name.
Are you building a site that does not use ActiveRecord? If that is the
case, setup your environment to exclude the ActiveRecord framework
(see comments in environment.rb).
Yeah, I ended up disabling ActiveRecord for the app and that did the
trick. The main thing is that it was a different behavior from Rails 1.2
(which the app has been until today). I’ve either had Rails 1.2 with no
db, or Rails 1.2 or 2.3 with MySQL, so I had not seen this never-die
sqlite file before.
Thx
– gw
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.