Re: Auto generate url patterns

On 12/8/06, leanmeandonothingmachine <[EMAIL PROTECTED]> wrote: > > I did want to use flatpages but can't for the 2 reasons in my orginal > post, unless I'm wrong about those limitations, in which case flatpages > would be perfect. > > I understand about urls being a collection of patterns, but I

Re: Auto generate url patterns

I did want to use flatpages but can't for the 2 reasons in my orginal post, unless I'm wrong about those limitations, in which case flatpages would be perfect. I understand about urls being a collection of patterns, but I don't see how I can make a pattern that fits when I won't have a set

Re: Auto generate url patterns

On 12/8/06, leanmeandonothingmachine <[EMAIL PROTECTED]> wrote: > The client is going to provide a list of arbitary urls that they wants > ei: about/, about/history/, contact/, services/, etc... and they need > to be able to add or remove urls using the admin interface, no changing > the url.py

Re: Auto generate url patterns

I'll try to be a little clearer with what I need. The client is going to provide a list of arbitary urls that they wants ei: about/, about/history/, contact/, services/, etc... and they need to be able to add or remove urls using the admin interface, no changing the url.py file. So there will be

Re: Auto generate url patterns

On 12/8/06, leanmeandonothingmachine <[EMAIL PROTECTED]> wrote: > > Noob question: I've just started getting into django, and wanted to get > opinions on auto generating url patterns from a db. Is that bad > practice, will it slow down the site? Depends on exactly what you are planning, and how

Auto generate url patterns

Noob question: I've just started getting into django, and wanted to get opinions on auto generating url patterns from a db. Is that bad practice, will it slow down the site? I'm thinking of doing this for a few reasons: 1) The client is very particular about the path. So I want to use one app