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.
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.