Errors when using tower sessions with sqlite store

[CriusDe]

Hi,

we get some errors in our application after the switch from axum sessions to tower sessions.

let pool = SqlitePool::connect(":memory:").await.unwrap();

let sqlite_store = SqliteStore::new(pool);
sqlite_store.migrate().await.unwrap();
tokio::task::spawn(
    sqlite_store
        .clone()
        .continuously_delete_expired(tokio::time::Duration::from_secs(10)),
);

let session_layer = SessionManagerLayer::new(sqlite_store)
    .with_secure(true)
    .with_expiry(Expiry::OnInactivity(Duration::hours(2)));

This is our init of the session store that is called once on server startup.

failed to save session err=error returned from database: (code: 1) no such table: tower_sessions
error=error returned from database: (code: 1) no such table: tower_sessions

these are our error logs we receive all the time.

Does anybody have an Idea or hint what the problem may be?

[maxcountryman]

Does the SQLite example work for you independent of your application?

Regarding your application, if the migration is succeeding then it's strange you'd see such an error. Are you sure the migration is working as expected?

[maxcountryman]

now switched to the in memory sqlite store

Have you considered using MokaStore instead? The primary difference is the LRU cache is bounded (altho Moka might allow you to configure an unbounded cache if you wanted) and of course the fact it's intended specifically for in-memory use.

[CriusDe]

Yeah i thought about that, i will give it try. Do you recommend using just the moka store or with sqlite as a backend like in the examples?

[maxcountryman]

I would recommend using MokaStore directly, at least at first. If that's working as expected, then you could use it with CachingStore and some other store (usually this second store would be persistent).

If using SQLite, in-memory might not be the best choice for a production setting. That's why the axum-login examples use a persistent file path.

[maxcountryman]

Regarding SQLite, in case it's something you do want to explore more, there's also the Rusqlite store: https://github.com/patte/tower-sessions-rusqlite-store. It's possible it could perform more reliably for your use case.

[CriusDe]

Ok thanks for your input, i will try and have a look at these solutions, to see what performs best