That is very good news! I'll see what I can do about the Doctrine test part.
Maybe when I'm done we could then open a ticket with both patches attached?
That would improve the chances of the patch being accepted soon and DbFinder
updated for symfony 1.4.
One potential problem is that the admin
Hey there,
first: I think Fabien was just kidding when he said Then, use plain PDO. :)
So, here's one for you. I have the DbFinderPlugin working (at least, kinda)
under symfony 1.4 (!).
If you want I can post a diff here. There's one thing I couldn't figure out as
of yet but that could be a
Alright, there you go, it's really only 2 lines changed at this time. :)
Report back if you're hitting any roadblocks but my app uses hydration/joins
quite extensively and it works just like before (minus that little bug I
mentioned which I have to hunt down today, will report back if it's
Frosty wrote:
+1 for a DbFinderPlugin support for Symfony = 1.3.
I even think that such a piece of code should be part of Symfony core.
I don't mind if I work with Propel, Doctrine or
AnyOtherSuperFutureORM. I just want it to query my DB.
You don't mind? Are you kidding? Then, use plain
Tony Piper wrote:
+1 from me. It would be great if François could update it for Propel
1.4 and Symfony 1.3/1.4 compatibility - it would probably take him
just a few minutes (relative to how long it would take me)…
The lack of DbFinder is a show-stopper for my 1.2-1.3 upgrade testing
and
It would be indeed nice if some effort could be made to get this plugin
working on symfony 1.3/1.4. I can't migrate my 1.2 project to 1.3 as it
heavily depends on this plugin. My original plan was to migrate my project
at some point in the future to Doctrine and ease the transaction-pain by
