Daniel Krol aa691dbc09 Use verify_token=null as verified to avoid unique constraint ... We were using verify_token="" to mean that the user was verified. We need a unique constraint on verify_token to prevent two users from getting the same verify link in their email. This means that if we have two verified users, they will both have verify_token="", which triggers the unique constraint. Oops. However, null is an exception to unique constraints, so we're now using that instead to mean verified.		2022-08-13 22:15:19 -04:00
..
paths	Mailgun integration	2022-08-13 14:26:04 -04:00
account.go	Use verify_token=null as verified to avoid unique constraint	2022-08-13 22:15:19 -04:00
account_test.go	Use verify_token=null as verified to avoid unique constraint	2022-08-13 22:15:19 -04:00
auth.go	Make error message more accurate. Rename test.	2022-07-29 15:52:23 -04:00
auth_test.go	Mailgun integration	2022-08-13 14:26:04 -04:00
client.go	Comment	2022-07-29 20:34:47 -04:00
client_test.go	Mailgun integration	2022-08-13 14:26:04 -04:00
integration_test.go	Mailgun integration	2022-08-13 14:26:04 -04:00
password.go	Make error message more accurate. Rename test.	2022-07-29 15:52:23 -04:00
password_test.go	Mailgun integration	2022-08-13 14:26:04 -04:00
server.go	Mailgun integration	2022-08-13 14:26:04 -04:00
server_test.go	Use verify_token=null as verified to avoid unique constraint	2022-08-13 22:15:19 -04:00
wallet.go	Server test/implement send verify-account email	2022-07-27 19:45:09 -04:00
wallet_test.go	Mailgun integration	2022-08-13 14:26:04 -04:00