[TYPO3] [Typo3] How large of website can typo3 handle?

Dennis Cheung hkdennis2k at gmail.com
Sat Jan 7 01:56:02 CET 2006


> If the folks at MySQL AB were really adventurous, they should look at adding
> a function like Oracle's "Connect By".  This works in a similar manner but
> is flexible enough where you can use the traditional parent-child
> associations in the database and the select statement is pretty straight
> forward.  You can also apply this select statement to other tables what were
> not necessarily set up to be part of a hierarchy, like in a data mining
> application.

I read some blog say they are already working on it(5.0 or 5.1?? I
don't remember).



>
>
> John C. Wilson
> Maximo Consultant
> Science Applications International Corporation (SAIC)
> (281) 552-2745
> john.c.wilson at saic.com
> -----Original Message-----
> From: typo3-english-bounces at lists.netfielders.de
> [mailto:typo3-english-bounces at lists.netfielders.de] On Behalf Of Bernhard
> Kraft
> Sent: Thursday, January 05, 2006 9:08 PM
> To: typo3-english at lists.netfielders.de
> Subject: Re: [TYPO3] [Typo3] How large of website can typo3 handle?
>
> Dennis Cheung wrote:
>
>
> > Even we better choice.
> > http://dev.mysql.com/tech-resources/articles/hierarchical-data.html
> > long inner join and Nested Set Model are useful to reduce total number
> > of queries.
>
> This is VERY interesting !
>
> I programmed hierarchial structures inside relational database for half a
> decade
> now ... and I knew that there was something around called nested sets ...
> but
> I never saw such a clear and easy to understand (or pherhaps just my
> apprehension
> has improved :) description of this method.
>
>
> If I find some time I will try to make a patch for CVS version of T3 which
> replaces
> the parent-method to store the pages table by this approach ... but this
> will require
> a lot of changes in many core methods (all which access pages by their
> parent :(
>
>
> Let's look what speed improvement comes out ... But please note that
> changing this would
> break all extensions already messing around with the pages table not using
> the API methods.
>
> (AFAIK currently there exist no API methods to "create" a page except
> tcemain - so if anybody
> creates/deletes pages in his extension and not uses the API methods but
> plain exec_DELETEquery
> or exec_INSERTquery's those extensions will all break ...
>
> So pherhaps this would be fine for T3 5.0 :)
>
>
>
> greets,
> Bernhard
>
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
>



More information about the TYPO3-english mailing list