You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, as you can see, in both PostgreSQL checkpoint implementation, the table names are fixed. It is forced to use checkpoint_migrations, checkpoint_blobs, checkpoint_writes to store all data. What if these names are already exist in the database? There will be conflicts when setting up this. So I'm suggesting we can add a common prefix before the table names. By adding the prefix, we can support using existing database with checkpoint* name and we can also support save multiple agents' checkpointer into one database.
This idea is also posted in langgraph-checkpoint-mysql repo, see tjni/langgraph-checkpoint-mysql#67
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, as you can see, in both PostgreSQL checkpoint implementation, the table names are fixed. It is forced to use
checkpoint_migrations
,checkpoint_blobs
,checkpoint_writes
to store all data. What if these names are already exist in the database? There will be conflicts when setting up this. So I'm suggesting we can add a common prefix before the table names. By adding the prefix, we can support using existing database withcheckpoint*
name and we can also support save multiple agents' checkpointer into one database.This idea is also posted in langgraph-checkpoint-mysql repo, see tjni/langgraph-checkpoint-mysql#67
Beta Was this translation helpful? Give feedback.
All reactions