Open obervinov opened 2 months ago
Structure of table users_requests
user_id
-> str
message_id
-> str
chat_id
-> str
authentication
-> str
authorization
-> str
timestamp
-> datetime
rate_limits
-> datetime
Structure of table users
user_id
-> str
chat_id
-> str
status
-> str
Is your feature request related to a problem? Please describe. Add an additional
PostgreSQL
backend to store historical user data (in addition to Vault).Describe the solution you'd like All user configuration should still be stored in the
Vault
. Postgres will serve as a repository of historical data. Adding the functionality of this backend will be minor and should require explicit inclusion when initializing theUsers()
class. Postgresql should store:Describe alternatives you've considered None
Additional context Adding postgresql, in the future will help to greatly expand and simplify the work.