Commit Graph

7 Commits

Author SHA1 Message Date
452796556f tell: fix sending unique constraint violating message multiple times 2021-03-09 15:17:20 +00:00
98646f3226 minor bugfixes 2020-05-01 23:20:37 +00:00
e03f5d0a43 add auto reconnect for postgres
This only works on the second database interaction, since psycopg2 only notices that
the connection is gone, when a query is executed.

So in the common case reconnect works as follows:
- some bot method calls a cursor function like .execute(), .fetchone(), etc.
  - this raises an error if the connection is broken
  - if following code then requests a new cursor, this will also fail since psycopg2
    now knows that the connection is gone
  - the error is caught in storage.DBConn.cursor(), a new connection will be set up
    of which a new cursor is yielded
If the error happens in connection.commit() or .rollback() instead we can instantly
reconnect since these methods are wrapped.

So why not wrap the cursor methods as well?
Consider the following example:
A query is the last thing that was executed on a cursor.
The database connection is lost.
Now .fetchone() is called on the cursor.
We could wrap .fetchone() and reconnect, but we'd have to use a new cursor since
cursors are linked to connections. And on this new cursor .fetchone() wouldn't
make any sense, since we haven't executed a query on this cursor.
2020-03-16 21:51:32 +00:00
Cephra
0c80766098 now with .format :D 2017-08-23 13:01:19 +02:00
Cephra
8eaffb0b99 changed to .notice 2017-08-23 12:59:00 +02:00
Cephra
3c38c5055e added feedback 2017-08-23 12:49:17 +02:00
mrhanky
f33a17038a
Huge cleanup and refactoring :> 2017-08-22 17:43:48 +02:00