(05-20-2019, 06:35 AM)MGatner Wrote: The issue isn't with your database group but rather with a table in your database that is expected to have a `group` column which is missing. I'd bet 99% that this is the `migrations` table which is created automatically upon using migrations and should look like this:
+-----------+--------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-----------+--------------+------+-----+---------+-------+
| version | varchar(255) | NO | | NULL | |
| name | varchar(255) | NO | | NULL | |
| group | varchar(255) | NO | | NULL | |
| namespace | varchar(255) | NO | | NULL | |
| time | int(11) | NO | | NULL | |
+-----------+--------------+------+-----+---------+-------+
If you have access to the database check the integrity of you migrations table and either repair it by adding `groups` or (if you haven't run any migrations yet) drop it and the framework will recreate it.
I miss some info in the docs that the table migrations is created automatically when using migrations.