-
-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manage database and schema using an ORM #2859
Comments
Not an ORM. Bad idea. I have a long term plan to migrate to using doctrine dbal with schema defined in json. We do this in the day job and it's very good. |
That's the plan, at least in core. Mongo has many many problems |
i have been playing around with this lately but there is one small thing , is it ok to brake a little bit of backward compatibility ? More like 2.0 update ? |
I was playing around with \Idno\Data\MySql recently and I changed few queries from the once that are hard coded to the once that are generated form DBAL query builder - https://www.doctrine-project.org/projects/doctrine-dbal/en/latest/reference/query-builder.html#sql-query-builder using DBAL query builder is a much easier fix to implement than using a full fledged ORM |
Currently database upgrades and schema changes are handled internally using SQL. This is prone to failure (see #2783).
We should port to Eloquent if possible, or Doctrine if we have to.
I'm not asking anyone else to do this - I'm planning on looking at this.
The text was updated successfully, but these errors were encountered: