Orm

aaricpittman wrote on Friday, January 08, 2016:

I was wondering what other developers thoughts are about implementing an ORM into the project. I know from searching past post that this has been discussed before but did not see a definitive answer and I’ve seen a couple of implementations in the code base.

My knowledge of PHP and the PHP ecosystem is limited, my background is in Ruby. However, I have been playing with implementing Eloquent, https://laravel.com/docs/5.1/eloquent-relationships#introduction, into the project with some success. I’m pushing my work to a branch in my fork on github, https://github.com/aaricpittman/openemr/tree/feature/eloquent . Would be interested in hearing your thoughts.

Aaric

(brady edited this to fix the github link)

qlcorp wrote on Monday, January 11, 2016:

We are doing MySQL renovations, and from what we have seen you’d almost have to rewrite the application to do that.

aaricpittman wrote on Friday, January 15, 2016:

I completely understand what you are saying. I’ve been working on a pharmacy model and implementing it into Administration->Practice->Pharmacies and it has been interesting.

However, it doesn’t have to be completed all at once. The work I have in the above branch is siloed and as far as I can tell doesn’t affect the rest of the application. And any new features could be required to make use of the orm.