Skip to content

Revisions

  • Remove extra comments

    @janko janko committed Dec 11, 2022
  • Expand using separate tables

    @janko janko committed Dec 11, 2022
  • Show setting likely foreign key column names for secondary configuration

    @janko janko committed Dec 11, 2022
  • Show setting `inheritance_column` to `nil` instead

    @janko janko committed Dec 11, 2022
  • Remove workarounds addressed in newest Rodauth version

    @janko janko committed Oct 21, 2022
  • Couple of fixes to make it functional today

    @janko janko committed Oct 1, 2022
  • Improve guide for handling account types, add separate tables

    @janko janko committed Oct 1, 2022
  • Fix typo in column name

    @janko janko committed Sep 29, 2022
  • 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`.

    @janko janko committed Jun 25, 2022
  • Lil more readable

    @dhnaranjo dhnaranjo committed Jun 24, 2022
  • Just using `select` returned a structure of [{account_id: #}], when we just want an array of ids.

    @dhnaranjo dhnaranjo committed Jun 24, 2022
  • Revert id removal from migration and change query to use subselect instead of a join

    @jaahoo jaahoo committed May 30, 2022
  • 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.

    @jaahoo jaahoo committed May 29, 2022
  • Update account types page with named auth classes

    @janko janko committed Dec 8, 2021
  • Add account types guide

    @janko janko committed Nov 6, 2021