MySQL - Including an INT column in Pivot Table Causes invalid SQL Query

[adrianpaiva1]

Looks like the type is listed incorrectly as 'integer' for MySQL instead of 'int'. I'm not sure if 'integer' is used in another DB variation so I left it, happy to remove it if needed.

Including an integer column in the 'getPivotColumns' method with Graphs leads an invalid SQL query with MySQL8 and produces - cast(null as int unsigned) as pivot_my_int_column

calling $my_model->descendantsAndSelf()->get() produces an invalid query.

[staudenmeir]

Hi @adrianpaiva1,
Thanks, I'll take a look.

[staudenmeir]

I removed the integer type, it's not valid anymore. Laravel 11 changed the way these types are determined and I missed the change from integer to int.

[staudenmeir]

Thanks! I released a new version.