Adk DatabaseSessionService migration not happening with same or existing db

[deepakbatham572]

when we are using session service as DatabaseSessionService and as per the below documentation

https://google.github.io/adk-docs/sessions/session/#the-session-lifecycle

it is creating our own table to manage the chats and events and now the new version is released

https://google.github.io/adk-docs/sessions/session/migrate/

when we are migrating the database we are not able to upgrade the same database or migrate the same database the source and destination db it is accepting which is different. and this is a big issue we can't create new db for production server and migrate again and again

we are created our own table as well and we are managing with the sql alchemy and alembic for migration and to update any thing any schema we can able to migrate or upgrade the existing db with alembic.

Can we migrate the existing db which is best to control ?
Or Can we create our own custom session service which it accept we can manage fully ?

[deepakbatham572]

Hi @GWeale , can you please help here ?

[wuliang229]

@deepakbatham572 right now the migration only works for different databases, but we are working on something that can do the migration in place. Feel free to implement a custom session service to work around the restriction for now.