This project is archived and is in readonly mode.
establish_connection causes ActiveRecord::StatementInvalid: SQLite3::BusyException: database is locked
Reported by Jens | August 22nd, 2010 @ 10:49 PM
In Rails 2.3.8
With the configuration below (and rails project attached)
Second.create fails with Sqlite3::BusyException.
Removing establish_connection, it will work again.
/////////////// MODELS
class First < ActiveRecord::Base
establish_connection :development
belongs_to :second end
class Second < ActiveRecord::Base
has_one :first, :dependent => :destroy establish_connection
:development
def before_validation_on_create
build_first
end end
////////////////// WITH MIGRATIONS
lass CreateFirsts < ActiveRecord::Migration
def self.up
create_table :firsts, :id => false do |t|
t.references :second
t.timestamps
end
end
def self.down
drop_table :firsts
end end
class CreateSeconds < ActiveRecord::Migration
def self.up
create_table :seconds do |t|
t.timestamps
end
end
def self.down
drop_table :seconds
end end
Comments and changes to this ticket
-
Jens August 22nd, 2010 @ 11:05 PM
What i can conclude is that since I use establish_connection in all models, they will not share connection pools at all. Even though they could (since they connect to the same database). This causes two different connections to access the sqlite file causing the lock.
Any feasable options here?
-
Jens August 22nd, 2010 @ 11:19 PM
This willa ctually fix it. Maybe this should close the "bug"?
class Legacy < ActiveRecord::Base
establish_connection :some_other_db self.abstract_class = true end -
-
-
Santiago Pastorino February 2nd, 2011 @ 04:33 PM
- State changed from “new” to “open”
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
Santiago Pastorino February 2nd, 2011 @ 04:33 PM
- State changed from “open” to “stale”
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
Jens