Hi all This issue: Started work on migrating to Ecto3, ran into issues with Sqlite's `busy` · Issue #244 · elixir-sqlite/sqlite_ecto2 · GitHub I’ve been trying a gung-ho approach to updating ecto_sqlite2 to support ecto3, and on the surface it seems to be straightforward enough: implement the new …

Not sure you can get any guarantees since the library is only guaranteed to work with Ecto 2. But, in this case maybe you just haven’t opened it with the right mode (should be serial).

Not sure you can get any guarantees since the library is only guaranteed to work with Ecto 2. That’s why I’m attempting to port it to Ecto 3 :slight_smile: in this case maybe you just haven’t opened it with the right mode (should be serial). Thank you, I’ll look into that! (even though the un…

:waving_hand: AFAIK Ecto 3 locks tables and uses two connections to the db during migrations. Maybe you can use some combination of :migration_lock option and the number of connections pool_size: 1 to work around your problem. I couldn’t make your example work since it’s missing a dependency: Un…

Well, I am authoring an sqlite3 Elixir library (which is a bridge to an excellent Rust library) but life hasn’t been kind this year and I am just beginning to recover and might resume work on the first stable release Soon™.

Ah! Thank you for the tip on the migration_lock_option! I’ll definitely look into that. I couldn’t make your example work since it’s missing a dependency: Replace {:sqlitex, "~>1.7.1", path: "deps/sqlitex"} with {:sqlitex, "~>1.7.1"} in mix.exs. I use path to sprinkle dependencies’ code with IO.…

Just tried migration_lock: nil, pool_size: 1 and got a different error: ** (DBConnection.ConnectionError) could not checkout the connection owned by #PID<0.304.0>. When using the sandbox, connections are shared, so this may imply another process is using a connection. Reason: connection not avail…

I should’ve inspected more Basically, the tests end up opening multiple connections anyway. For TestRepo: {:connect, [ pool_index: 1, repo: Ecto.Integration.PoolRepo, telemetry_prefix: [:ecto, :integration, :pool_repo], otp_app: :ecto, timeout: 15000, adapter: Sqelect, databa…

Hello :waving_hand: I am rather fond of Sqlite and thought it would be fun to update sqlite_ecto2 so it works with Ecto 3. I have hit the same {"busy",0..5} issue as @dmitriid . This appears to be due to the Ecto migrator running the migration in a transaction via an async task, but before the tra…

Hi @Lankester and @dimitarvp , have you made some progress on your implementations of Sqlite3 / Ecto3 ? I would be glad to help. PM me :slight_smile:

Ah, I’ve got nothing to hide. Recently started a new job and it’s taking most of my time – initial good impressions, you know. Also due to the closure of the gyms I got hit by very low energy levels and I am not motivated to work on anything beyond the main job. Happily though both things will co…

Elixir Programming Language Forum

Help with debugging sqlite's 'busy' error with Ecto3

Questions & Help Questions

lud February 1, 2021, 9:27am 13

Today is treadmill day ! I wish you well