F1.02 Apache Php Laravel. What's wrong with Eloquent ORM (Wpf, Xamarin, Angular SPA, Reactjs SPA) - chempkovsky/CS2WPF-and-CS2XAMARIN GitHub Wiki

Note 1:

Under the requirements Laravel controllers should work with the storage created by another platform (for instance Entity Framework).

Note 2:

Read "Composite" primary keys article.

They say: Eloquent requires each model to have at least one uniquely identifying "ID" that can serve as its primary key. "Composite" primary keys are not supported by Eloquent models. However, you are free to add additional multi-column, unique indexes to your database tables in addition to the table's uniquely identifying primary key.

This conflicts with storage requirements.

What do they have in return?

• They have Query Builder with an abstraction layer implementation.
• They have, Database: Migrations with an abstraction layer implementation.

Query Builder and Database: Migrations-tool hide specific of the any SQL-server. We mean, business logic written for MySql should work for Ms Sql server and vice versa. Migration code written for MySql should work for Ms Sql server and vice versa. It's more than enough for us.