SCIF
commented
6 years ago Hi @oschonrock ,
Thanks for detailed question. Unfortunately, I haven't used Propel <2 so can't estimate possibility of such adoption and do it. I'm pretty sure, you can develop your own UserProvider to be able to authorize users managed by Propel. The rest of responsibility of package is just "sugar" like command integration and connection arrangement.
Personnaly, my advice, take a look onto Symfony + Doctrine and think about rebuild your app with that tools.
Background
So I am a "version stuck".
We have a 6 year old web application with 100+ table and 20Gb of data. The web framework needs changing and the frontend UI needs needs replacing.
Currently leaning towards laravel (because as a web framework it seems OK, and popular so easy to hire staff, probably with a vue.js frontend...i know don't ask).
I have been using propel since 1.2 when Hans transpiled it all from Apache Torque. Back then we used to contribute. (The whole idea of integrating the instance pool was ours). The legacy application is based on propel 1.7. We never changed to propel 2, because a) no need 1.7 is just fine. b) propel2 is alpha, we need stability for the ORM. We don't mind active record, we like all the generated code, we like the ModelQuery classes. We know the vageries like accidental cascade save via cached instances in the pool..etc. We use NestedSet and Sorted behaviours...It's all good.
We hate doctrine, because it is a black box. In propel i can just delve into the classes and start debugging if I don't understand, it becomes obvious in < 10min. Also Doctrine is way slow compared to propel for obvious reasons. We don't find that the Base* classes get in the way of the domain model (mostly).
Eloquent seems terribly incomplete compared to Propel 1.x (or doctrine obviously). It really doesn't give you much at all. Might was well write SQL?
So ideally we would actually like to stay with propel 1.7 and use our existing codebase. That part is not really broken. But switch to laravel.
Question
Sorry, long intro, here goes the question:
Could this PropelLaravel package be easily adapted to integrate Propel 1.7 into Laravel 5.5?
I realise you wouldn't do that, but it looks like there is not a million lines of code here, so maybe we can just pick this up, fork it and then we have what we think(!) we want: Propel 1.7 + Laravel 5.5.
Does that make sense?
Many Thanks