I occasionally try to delete an account record from the console while testing, and most of the time it fails because there is an associated record with a foreign key referencing that account, blocking the deletion (usually a remember key record).
I wanted to ask, what do you think in general about setting `on_delete: :cascade` on foreign keys on Rodauth tables referencing the accounts table? If you think it's safe in general, would you accept a PR that updates the README to show setting `on_delete: :cascade`? Personally, that's how set up most of my foreign keys in applications I work on, as it often simplifies deletion in application code.
I'm thinking of adding this to rodauth-rails' Active Record migrations, but I try not to diverge too much from the recommended way. Alternatively, I'm already developing a module that would automatically define Active Record associations based on Rodauth configuration, so there I could set up `dependent: :destroy`. But I generally prefer doing it on the database level.