Replies: 2 comments 1 reply
-
You could pass a mutable string, and use String#replace to update it if the information needs to be changed (a mutable hash instead of a mutable string is also possible). Not exactly good design, but having authentication information change without your control is not good design either. :) Note that if a connection to the database fails, Sequel raises a Sequel::DatabaseConnectionError exception, so you could rescue that. |
Beta Was this translation helpful? Give feedback.
1 reply
-
I added 8a18971 which I think should be able to handle your use case. Could you try it out and provide feedback? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am connecting to a postgres database. user password may be changed/rotated at arbitrary times by an external entity.
all my connections are setup during
Sequal.connect
during client service startup. If the connection is dropped/or session timed out for some reason, reconnection is not possible because connection string is no longer valid.my ask is
just the second one could be enough to move forward, I can put up a periodic tasks to update the connection string on the client service side if needed.
Beta Was this translation helpful? Give feedback.
All reactions