We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Remove extra comments
Expand using separate tables
Show setting likely foreign key column names for secondary configuration
Show setting `inheritance_column` to `nil` instead
Remove workarounds addressed in newest Rodauth version
Couple of fixes to make it functional today
Improve guide for handling account types, add separate tables
Fix typo in column name
Revert last changes Using SQL subqueries is completely valid; they reduce the number of SQL queries being executed, avoid loading unnecessary data into memory, and make the main query more intuitive (when we see the list of IDs in SQL logs, we don't know where they came from). Additionally, the non-existing `account_roles` table was used, so we change it back to `account_types`.
Lil more readable
Just using `select` returned a structure of [{account_id: #}], when we just want an array of ids.
Revert id removal from migration and change query to use subselect instead of a join
Hi, with id on account_types table I have 'PG::AmbiguousColumn: ERROR: column reference "id" is ambiguous' error in account_ds method. After I set id to false everything works. I tried to update the join query to works but I couldn't make it.
Update account types page with named auth classes
Add account types guide