@admin-8
Google Login and traditional email and password login are two different methods of authentication.
Google Login, also known as Google Sign-In, is a secure way to log into websites and apps using your Google account credentials. When you sign in with Google, you are asked to grant access to your Google account information, and you are then logged into the website or app using that information.
Traditional email and password login, on the other hand, requires you to create an account with a unique email address and password. When you sign in, you enter your email and password to access your account.
Posts made by langnerfrancesco
-
RE: How to distinguish between Google Logins and traditional email+pwd logins?
-
RE: SQL error on request_frequencies Table
@becharam said in SQL error on request_frequencies Table:
I had a problem with fusion and the server stopped working. The last log I found was this one:
Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "request_frequencies_uk_1"
Detail: Key (tenants_id, type, request_id)=(74eeee80-d400-4540-a377-de1e4a7239dc, 0, 94159bc9-4b03-4735-ae23-0ab33745e82b) already exists.
11:37Error updating database. Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "request_frequencies_uk_1"
Detail: Key (tenants_id, type, request_id)=(74eeee80-d400-4540-a377-de1e4a7239dc, 0, 94159bc9-4b03-4735-ae23-0ab33745e82b) already exists.
The error may exist in io/fusionauth/api/domain/RequestFrequencyMapper.xml
The error may involve defaultParameterMap
The error occurred while setting parameters
SQL: INSERT INTO request_frequencies (count, last_update_instant, request_id, tenants_id, type) VALUES (?, ?, ?, ?, ?)
Cause: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "request_frequencies_uk_1"
Detail: Key (tenants_id, type, request_id)=(74eeee80-d400-4540-a377-de1e4a7239dc, 0, 94159bc9-4b03-4735-ae23-0ab33745e82b) already exists.
There is no error pointing to a memory overload, and I am not sure why the server stopped.
Any help on why the server might have stopped would be appreciated
Facing same issue here. Help is appreciated.