Hello, recently we had to implement your driver into our Laravel project because of (hoping) a temporary solution to store files. The good news is it's awesome, the bad news came when we were told to migrate to SQL Server.
We made a little test on a fork for this driver and made it successfully compatible with SQL Server (tested on SQL Server 2019), both migrations and functions.
We didn't generalize the implementation since it should be temporary for us and a fork with the changes is sufficient, but could there be an interest for a pull request if the work is properly done?
Hello, recently we had to implement your driver into our Laravel project because of (hoping) a temporary solution to store files. The good news is it's awesome, the bad news came when we were told to migrate to SQL Server.
We made a little test on a fork for this driver and made it successfully compatible with SQL Server (tested on SQL Server 2019), both migrations and functions.
We didn't generalize the implementation since it should be temporary for us and a fork with the changes is sufficient, but could there be an interest for a pull request if the work is properly done?