This project is archived and is in readonly mode.
establish_connection causes ActiveRecord::StatementInvalid: SQLite3::BusyException: database is locked
-
Jens
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
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 -
Jens
That is, if First, and Second inherit from Legacy.
-
Santiago Pastorino
- 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
- State changed from open to stale
