Perfect, thank you for taking the time to do it.
Kupo
Carsten Schumann wrote:
> Hi Kiril, hi folks!
>
> I just finished my port of the nested set plugin to Propel 1.3. When
> the patch is applied, the plugin shall work with Propel 1.2 and Propel
> 1.3 since there is an automatic swich at the s
Hi Kiril,
i will track down all changes i did on the nested set plugin in our
repository and provide a patch which will use your switch to maintain
compatibility to propel 1.2
Carsten
On 10/20/07, drmikecrowe <[EMAIL PROTECTED]> wrote:
>
>
> We need some method for folks working on Propel13 to c
We need some method for folks working on Propel13 to collaborate. I
ported sfPropelFileStoragePlugin, and have sfGuard too (I don't think
any changes were needed for it).
On Oct 20, 1:26 am, Kiril Angov <[EMAIL PROTECTED]> wrote:
> I had to port one other plugin to Propel 1.3 and I was thinking
I had to port one other plugin to Propel 1.3 and I was thinking at that
time that just fixing it for me will not suffice so I was wondering at
that time how to make the changes not break support for Propel 1.2 and I
came to the following conclusion.
if (method_exists(new TagPeer(), 'doSele
Hi Frank,
you are not right at all with the nested sets.
Yes, Propel 1.3 supports nested sets.
No, they are not compatible with the symfony plugin. The symfony
plugin offers the possibility to store more than one tree in one table
using several tree scopes. Propel 1.3 does not support such a scop
The Propel 1.3 team are working on the debug stuff - allegedly it's
the only thing holding back the 1.3 release.
I ninja'ed in some debug for sfPropel13Plugin, but didn't bother
finishing up when I found out their plans.
It's better than nothing for now, but not by much.. That's one thing I
miss
>> but many problems with other plugins as well (e.g. the nested set
one)
Propel 1.3 has nested set support natively, so the nested set plugin
is absolete. I use Propel 1.3 in a non-symfony application and it
works very well.
The disadvantage of Propel 1.3 is currently the lack of debug
Hi Fabian,
Thanks for the clarification.
> but many problems with other plugins as well (e.g. the nested set one)
Right, so that alone would be a big killer for me... I noticed the
warnings on custom query changes.
I've just installed the patch, and I'll take a look at some
benchmarking la
Hi,
thats my blog.
We are also currently looking into Propel 1.3Plugin. looks promising, but many
problems with other plugins as well (e.g. the nested set one)
If my proposed patch for propel class generation does speed your code up
depends on you usage.
Check your generated classes for the i
Yeah, I've taken a look at briefly. I guess it's time to bite the
bullet and give implementing a try.
From the notes, there doesn't seem to be too mush todo.
Thanks,
Piers
On 16/10/2007, at 12:12 PM, Kiril Angov wrote:
>
> Piers Warmers wrote:
>> Hi all,
>>
>> I've just gone through my po
Piers Warmers wrote:
> Hi all,
>
> I've just gone through my posts after the weekend and noticed:
>
> _http://www.hma-info.de/blog/2007/10/13/better-performance-patch-for-symfony-10x-and-propel-12/_
>
> So I'm just wondering who's installed it and if there is any feedback
> on how much performanc
11 matches
Mail list logo
