Invalid column name errors

[kangabru]

This PR will make the composer throw errors if a query tries to use invalid column names.

Reasoning

Queries currently ignore invalid column names which makes it easy to write queries that break unexpectedly.
This can lead to errors such as when a 'where' clause returns more records than it should. This change will ensure the developer is aware of a bad query and fix the issue.

Example

• A model has fields like author_id and is_admin
• The developer writes a query like Model.query().where({ user_id: user.id, is_admin: false }).destroyAll(...)
• The developer made an easy mistake and used the column user_id. This doesn't exist on the model so Nodal silently ignores it. This query then selects and deletes all users by accident.
• This PR will fix issues like this by making a query like this throw an error to ensure this is never pushed to a deployed environment.

[jacoblee93]

I would write a new test case here instead of adapting an old one

[kangabru]

This is actually an issue with the existing tests since the column active doesn't exist (it's is_active). I had to update them because my new changes would break the tests otherwise. This column doesn't seem to affect the result of the test anyway since they still pass like this.

[jacoblee93]

Ah gotcha. Makes sense then

[jacoblee93]

Keep the style consistent with other tests (use the callback and catch the error)

[kangabru]

The way I wrote the code is such that it throws an error outside of the end() call. I did this is because it's more of a developer error, not a DB one. If I did it inside the end call then it might be less obvious.

Would you prefer me to have it throw the error inside the end() call?

[jacoblee93]

Add a test for comparators too (pets__name__ilike or __lt)

[kangabru]

Yeah I could add those if you like but this change was just to fix the bad column name used in the original test.