You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By design, every sqlite connection to :memory: returns a new in memory DB. This means in a connection pool, every connection is using a different DB and later connections do not see the tables created by running the migrations on the first.
It is possible to specify a name and shared cache for the connection but it doesn't seem to be possible for some connections to be read-only while others are read-write.
The text was updated successfully, but these errors were encountered:
I think this can be ignored as won't fix. The only reason for creating the read-only DB was to ensure sqlite errors were propagated correctly in tests and that can be done in simpler ways (see #86). It is possible to create a read-only DB in a tempfile but it's a faff (#85).
By design, every sqlite connection to
:memory:
returns a new in memory DB. This means in a connection pool, every connection is using a different DB and later connections do not see the tables created by running the migrations on the first.It is possible to specify a name and shared cache for the connection but it doesn't seem to be possible for some connections to be read-only while others are read-write.
The text was updated successfully, but these errors were encountered: