New database events schema in python
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 1k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 88
Description
Hi, I just checked on adk-python events table that it only uses single `events` column for storing jsonb of the event now. On the other hand, adk-go still uses separate column to store events information on different columns. Is there any plan to make adk-go using similar schema?
Currently Im trying to implement Gemini Live support for adk-go in #567, however im not able to store information about input and output transcription to the events table since there is no column for that. I am considering it cant be stored on the `content` column. Any suggestion?
Thanks!
Contributor guide
Research direction
The payload names the adk-go events table and related work in #567; start by reviewing the existing event schema and how that work records transcription data. Done means deciding on a schema that stores Gemini Live input and output transcription without relying on the content column, aligned with adk-python.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, python
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100