You can find my patch for the unit tests here: [ http://pastebin.com/f18abd80b
]. This passes all tests on MySQL. It probably can be improved, but
hopefully it is enough to motivate someone to start on the Doctrine
part!
Greetings,
Jan Fabry
On Dec 6, 3:53 pm, Daniel Lohse wrote:
> That is very
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
On Dec 3, 11:50 am, Daniel Lohse wrote:
> 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
thanks a lot, I'll test it right away :)
--
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to symfony-us...@googlegroups.com.
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.
Thanks Daniel. Even if there are only two lines, it's far better than
nothing :-)
BTW, I guess that a more serious maintenance for that plugin would be
very useful, but François Zaninotto (who used to maintain it) won't
have time for that until Propel 1.5 (see
http://groups.google.com/group/propel
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 somet
Great Daniel, thanks.
And yes, I think that your diff may be useful...
At least, I hope that using DbFinder, I will be able to write "ORM-
compatible" code for Symfony's future versions (I will try to
contribute in that direction as well)...
> first: I think Fabien was just kidding when he said "
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 p
Fabien,
Thanks for your quick answer.
> > 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 PDO.
Obviously, plain PDO does not offers the capability of an ORM.
I would like to use ORM "sta
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 pla
+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.
I shouldn't rewrite all queries and schemas if I need to switch ORM,
ju
thanks for answering, and of course each ORM has it's good parts.
For sure specific data logic has to be developed directly using ORM,
and I never said we have to ban ORM specific dev nor that DbFinder has
to implement nested set or geocode behavior. I just find it's a pity
it is no more maintaine
DbFinder is a bad choice for plugins that use the database in a
nontrivial way. Yes, it unifies things at the simplest level
(queries), but if you want to use the features that really distinguish
one ORM from another (column aggregation inheritance, behaviors,
migrations), you're out of luck. And i
+1
I really do like symfony because I can develop plugins for everything
and easily re-use code in every applications that needs it. As I
remember, jobeet tutorial encourages you to do so, Pirum release let
me think that Sensio labs wants us to create our own repository too,
so everything encourag
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
> a
ay, November 19, 2009 15:05
> To: symfony users
> Subject: [symfony-users] Re: DBFinderPlugin future
>
> On Nov 19, 12:20 pm, Gareth McCumskey wrote:
> > You can stick with Propel can't you? Doctrine is only the default plugin
> and
> > can be changed to use Propel
in by
temporary using the dbfinderplugin to write propel (criteria) queries.
Go go :-)
-Original Message-
From: Jan Fabry [mailto:jan.fa...@monkeyman.be]
Sent: Thursday, November 19, 2009 15:05
To: symfony users
Subject: [symfony-users] Re: DBFinderPlugin future
On Nov 19, 12:20 pm, G
On Nov 19, 12:20 pm, Gareth McCumskey wrote:
> You can stick with Propel can't you? Doctrine is only the default plugin and
> can be changed to use Propel instead.
Yes, the standard functionality of DbFinder might work (the simpler
querying), but I was thinking about the admin generator stuff.
Ho
18 matches
Mail list logo
