Disable soft deletes on LoginModel

[MGatner]

No description provided.

[lonnieezell]

The thought here was that it was better to never be able to easily delete a login attempt for logging reasons. Granted, someone could simply call purge as easily, but at least then they know what they're committing to :)

Maybe it would be better to update the migration to create the table that way?

[MGatner]

Hmm I see. The problem is that it essentially disables using any find() methods from the model since it adds the deleted_at field into the query causing a database error for "column not found". I think making them soft deletes is a fine solution for a little extra safety, or maybe overriding the model's delete() function with a dummy?

[lonnieezell]

Ah, then this solution is fine, actually. I'll merge. As long as the package itself doesn't delete any, there's really nothing to stop others from bad acts.

[MGatner]

Thanks! Though the idea of throwing an exception at those scoundrels from an overloaded model->delete() was granting me a pleasant sense of justice 😆 👨‍⚖