Laravel MySQL Spatial interferes with parallel testing

[osteel]

Hi,

First of all apologies because I don't really have time to investigate this.

We use Laravel 8's parallel testing feature in our CI pipeline and it recently broke. I've just realised that this started happening from the commit where I introduced this package.

I ran a quick test and can confirm that removing the Laravel MySQL Spatial package immediately fixed the issue.

For reference this is the kind of MySQL error it generates:

Doctrine\DBAL\Driver\PDO\Exception: SQLSTATE[HY000] [1049] Unknown database 'laravel_test_2'

It's like it's preventing the creation of separate database schemas for parallel processes somehow.

This may or may not be related to #147.

[desaintflorent]

I confirm that unfortunately, using Laravel 8's parallel testing feature with this package doesn't work.
Switching to classic testing is working.
Any news about this problem ?

[osteel]

@desaintflorent haven't heard anything yet – still using classic testing in the meantime

[Livijn]

I removed the support for changing columns that require custom Doctrine types. That is what interferes with Laravel's parallel testing. You can use this repo if you want: https://github.com/Livijn/laravel-mysql-spatial