Documentation Needed For Challenges/Missing Features

[nickpoulos]

Although advertised as MySql compatible, there are several gotchas and missing features from the typical Eloquent + MySql experience. These should be outlined in the docs somewhere.

An obvious one is that the default Laravel migrations do not run with this driver, there are modifications necessary, some pretty substantial like user emails uniqueness. But this goes for failed_jobs and others. See: https://usefathom.com/blog/multiple-uniques-singlestore

The other one is the lack of support for certain prepared statement operations. If you try to run php artisan migrate:fresh, for example, you will get an error.

I am sure there will be others once I get a chance to dive in more.

[AdalbertMemSQL]

Hey!
That's a brilliant good suggestion. I will create a ticket for this.

[timmaier]

Would also be interested in such a documentation piece.

Failed jobs, personal access tokens, users emails all usually have unique() constraints out of the box.

Having a best practices guide would be very helpful for these scenarios.