+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 migration plans. cheers, Tony. On Nov 19, 8:06 pm, "Daniel Kucharski" <[email protected]> wrote: > 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 > temporary using the dbfinderplugin to write propel (criteria) queries. > > Go go :-) > > > > -----Original Message----- > From: Jan Fabry [mailto:[email protected]] > Sent: Thursday, November 19, 2009 15:05 > To: symfony users > Subject: [symfony-users] Re: DBFinderPlugin future > > On Nov 19, 12:20 pm, Gareth McCumskey <[email protected]> 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 ofDbFindermight work (the simpler > querying), but I was thinking about the admin generator stuff. > However, it seems that does not even work too well under Symfony 1.2, > so it might be better to just go with 1.3, and do the required admin > changes manually, or with other plugins. > > Still, it would be nice to have a current, working and widely used > DbFinderPlugin, certainly with the transition to Doctrine as the > default ORM. Is anyone still motivated to look at the open bugs, or is > extra help required to get them fixed? > > Greetings, > > Jan Fabry > > > On Thu, Nov 19, 2009 at 11:18 AM, Jan Fabry <[email protected]> > wrote: > > > Hello, > > > > Is anyone working on updating DbFinderPlugin for Symfony 1.3/1.4, and > > > the included versions of the ORM frameworks? I don't know whether > > > François will spend more time on it, and I don't see any other > > > activity. > > > > I would like to use it for a new project, but I guess the best way to > > > do this is start with Symfony 1.2 now, wait for the plugin, and > > > upgrade to 1.3/1.4 when it is ready? > > > > If it is clear that no-one is planning to spend time on it, I might > > > try it. I come from a Propel background, but my knowledge of the > > > internals of Doctrine and Symfony needs work. > > > > Greetings, > > > > Jan Fabry > > > > -- > > > > You received this message because you are subscribed to the Google > Groups > > > "symfony users" group. > > > To post to this group, send email to [email protected]. > > > For more options, visit this group at > > >http://groups.google.com/group/symfony-users?hl=. > > > -- > > Gareth McCumskeyhttp://garethmccumskey.blogspot.com > > twitter: @garethmcc > > -- > > You received this message because you are subscribed to the Google Groups > "symfony users" group. > To post to this group, send email to [email protected]. > For more options, visit this group > athttp://groups.google.com/group/symfony-users?hl=. -- You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en.
