Hi folks,
I'm new to ADK and am trying to replicate the BIDI demos using SQLite for persistence.
Specifically, I'm working with the sample at:
https://github.com/google/adk-samples/tree/main/python/agents/bidi-demo
To test persistence, I configured SQLite and temporarily hard-coded the user_id and session_id inside the WebSocket endpoint:
from google.adk.sessions import DatabaseSessionService
db_url = "sqlite:///./adk_sessions.db"
session_service = DatabaseSessionService(db_url=db_url)
@app.websocket("/ws/{user_id}/{session_id}")
async def websocket_endpoint(websocket: WebSocket, user_id: str, session_id: str) -> None:
"""WebSocket endpoint for bidirectional streaming with ADK."""
user_id = "user_123"
session_id = "session_123"
logger.debug(f"WebSocket connection request: user_id={user_id}, session_id={session_id}")
await websocket.accept()
logger.debug("WebSocket connection accepted")
# rest of the code...My expectation is that if I reconnect to the WebSocket (with the same hardcoded user and session IDs), the session should be restored and previous conversation context should be loaded automatically.
However, this does not seem to be happening—each reconnection starts a completely fresh conversation, even though I see rows written to the events table in the SQLite DB.
So I'm unsure whether the session is being saved correctly, or whether it is being loaded but not applied.
Could you clarify:
- Does the BIDI demo automatically restore conversation state when a session ID is reused?
- Is any additional configuration required for
DatabaseSessionService when using SQLite?
- Which tables/columns should I inspect to verify that session and conversation state are actually being persisted?
Any guidance would be greatly appreciated!
Hi folks,
I'm new to ADK and am trying to replicate the BIDI demos using SQLite for persistence.
Specifically, I'm working with the sample at:
https://github.com/google/adk-samples/tree/main/python/agents/bidi-demo
To test persistence, I configured SQLite and temporarily hard-coded the
user_idandsession_idinside the WebSocket endpoint:My expectation is that if I reconnect to the WebSocket (with the same hardcoded user and session IDs), the session should be restored and previous conversation context should be loaded automatically.
However, this does not seem to be happening—each reconnection starts a completely fresh conversation, even though I see rows written to the
eventstable in the SQLite DB.So I'm unsure whether the session is being saved correctly, or whether it is being loaded but not applied.
Could you clarify:
DatabaseSessionServicewhen using SQLite?Any guidance would be greatly appreciated!