You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
One of the main advantages of using PHP as a backend language is the availability of affordable hosting, which is often not possible with other languages like Java. For example, I can get managed hosting with 6 GB RAM for just 3.70 € on sale. The main disadvantage is the lack of control over the database. You're usually limited to MySQL or, occasionally, MariaDB. While this cost difference may not matter to companies, for a small non-profit amateur theatre like ours, every euro we can save counts.
Describe the solution you'd like
Laravel already supports many SQL drivers, including MySQL and MariaDB. The query builder does all of the work by converting instructions into valid SQL code for the selected driver. The only issue arises when raw SQL gets used instead of Laravel’s query builder, for example, in the initial database migration.
Unofficial MySQL support wouldn’t take resources away from other features or development in general, as the goal wouldn't be to provide perfect compatibility or promote MySQL support in the official documentation. The goal is just to elliminate the current errors in db migration and in three other places where raw psql specific sql is used.
Additional context
.-
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
One of the main advantages of using PHP as a backend language is the availability of affordable hosting, which is often not possible with other languages like Java. For example, I can get managed hosting with 6 GB RAM for just 3.70 € on sale. The main disadvantage is the lack of control over the database. You're usually limited to MySQL or, occasionally, MariaDB. While this cost difference may not matter to companies, for a small non-profit amateur theatre like ours, every euro we can save counts.
Describe the solution you'd like
Laravel already supports many SQL drivers, including MySQL and MariaDB. The query builder does all of the work by converting instructions into valid SQL code for the selected driver. The only issue arises when raw SQL gets used instead of Laravel’s query builder, for example, in the initial database migration.
Unofficial MySQL support wouldn’t take resources away from other features or development in general, as the goal wouldn't be to provide perfect compatibility or promote MySQL support in the official documentation. The goal is just to elliminate the current errors in db migration and in three other places where raw psql specific sql is used.
Additional context
.-
The text was updated successfully, but these errors were encountered: