sharded-gotify/database
Jannis Mattheis 92a468bf74 Fix packets.go:36: unexpected EOF
Mysql has a setting called wait_timeout, which defines the duration
after which a connection may not be used anymore. Gotify doesn't
apply this, and expects the connection to work without timeout.

The fix is to set SetConnMaxLifetime, this however, isn't the
exact counterpart for wait_timeout on mysql. wait_timeout is
relative to the last use of the connection. The go setting
uses the creation of the connection as base.

Example error output:
```
[mysql] 2020/05/31 17:53:02 packets.go:36: unexpected EOF
[GIN] 2020/05/31 - 17:53:02 | 500 |     247.062µs |        10.2.2.1 | GET      "/application"
Error #01: an error occured while authenticating user

(/proj/database/client.go:24)
[2020-05-31 17:53:02]  invalid connection
```
2020-06-01 19:16:12 +02:00
..
application.go Use v2 in package path 2020-05-08 10:43:17 +02:00
application_test.go Use v2 in package path 2020-05-08 10:43:17 +02:00
client.go Use v2 in package path 2020-05-08 10:43:17 +02:00
client_test.go Use v2 in package path 2020-05-08 10:43:17 +02:00
database.go Fix packets.go:36: unexpected EOF 2020-06-01 19:16:12 +02:00
database_test.go Use v2 in package path 2020-05-08 10:43:17 +02:00
message.go Use v2 in package path 2020-05-08 10:43:17 +02:00
message_test.go Use v2 in package path 2020-05-08 10:43:17 +02:00
migration_test.go Use v2 in package path 2020-05-08 10:43:17 +02:00
ping.go Add health api 2019-08-16 09:28:57 +02:00
ping_test.go Add health api 2019-08-16 09:28:57 +02:00
plugin.go Use v2 in package path 2020-05-08 10:43:17 +02:00
plugin_test.go Use v2 in package path 2020-05-08 10:43:17 +02:00
user.go Use v2 in package path 2020-05-08 10:43:17 +02:00
user_test.go Use v2 in package path 2020-05-08 10:43:17 +02:00