What would you like to see?
Just want to raise concern about the behaviour of last updated at field in database. I don't know whether this is still on development/improvement or is a bug.
Currently, when chat is updated either via "Save", "Submit", or "Regenerate" (response), last_updated_at field does not seem to change.
For more context, "Submit" would:
- create new record in chat with createdAt == lastUpdatedAt
- hard delete all chats submitted after the edited chat
"Regenerate" would:
- create (replace) new record in chat with createdAt == lastUpdatedAt
What I use:
- Postgres for database
- AnythingLLM v1.15.0
What would you like to see?
Just want to raise concern about the behaviour of last updated at field in database. I don't know whether this is still on development/improvement or is a bug.
Currently, when chat is updated either via "Save", "Submit", or "Regenerate" (response), last_updated_at field does not seem to change.
For more context, "Submit" would:
"Regenerate" would:
What I use: