Problems running in-memory sqlite migrations containing spatial features

[grimzy]

Problems running in-memory sqlite migrations containing spatial features

[grimzy]

@ARTAEX, this package is intended to be used with MySQL and therefore will not work with Sqlite. If you look here, you can see that the Grammar is only loaded when the database driver is set to mysql.

I can only advise you to run your tests on a MySQL database because Sqlite doesn't have the same features, behavior, nor syntax.

If for you the time it takes for running the tests is an issue, you can look at into running MySQL in memory; but that has other implications.

It would be nice to document how to properly configure this package for testing.

Agreed! Maybe when I get the time. PRs are also most welcome :)

[MatanYadaev]

@grimzy Laravel doesn't support SQLite spatial columns and indexes, do you think there's a reason?

SQLite has an extension called SpatialLite, I guess you know it. Is this extension is not good enough to be implemented in the Laravel framework?
Or maybe Larave doesn't support this extension because no one asked for it, or no one sent a PR with this extension support? WDYT?

If Laravel was supporting this extension, do you think laravel-mysql-spatial package could also support SQLite? (with some adjustments)
Is that something you could accept?

I might be interested to take this as a project, as long it's feasible. I'll be glad to hear your opinion about it.