[drupal-devel] Path system scaleability

[Adrian Rossouw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I just came upon a solution that I think would work well.

We would :
1) add a url_alias column to the node table
2) modify node_load to use the url_alias column, if set, otherwise 
default to node/view/$node->nid, and set the $node->link variable.
3) change all l('node/view/ . $node->nid) to l($node->link);

Then pathauto can just implement the nodeapi hook to set the url_alias 
to whatever it wants, and the url_alias table will not
grow unruly.


I will be rolling a patch for this soon.




On 19 Apr 2005, at 2:23 PM, Moshe Weitzman wrote:

> I would think that we could employ a system similar to locale.module. 
> It translates a thousand of strings on a large page and seems to 
> perform adequately.
>
> -moshe
>
> Adrian Rossouw wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> I've recently found myself incredibly impressed with the autopath 
>> module, but I realize that there is an inherent scaleability issue
>> with how we do paths at the moment.
>> On every page load, the entire url_alias table is loaded into memory, 
>> and enabling the autopath module on a site like Drupal.org with 
>> thousands upon thousands of nodes, is just impractical. Does anyone 
>> have an idea of how we could make the path system
>> easier to use for large sites?
>> - --
>> Adrian Rossouw
>> Drupal developer and Bryght Guy
>> http://drupal.org | http://bryght.com
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.2.4 (Darwin)
>> iD8DBQFCZPIagegMqdGlkasRAsYLAJ0TBqKVHU+3QL9J2TgdVar/r2LHqgCfbmWu
>> zINs3OqZ7AO3lHFYCIMDHOY=
>> =7IEu
>> -----END PGP SIGNATURE-----
>
>
- --
Adrian Rossouw
Drupal developer and Bryght Guy
http://drupal.org | http://bryght.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFCZU6/gegMqdGlkasRAmbEAJ9b775ZxHDZN9SLNx4AA6pRDNLG0QCfVIH9
HHfsunWsGlY51H44aZahnh0=
=fwEw
-----END PGP SIGNATURE-----