On Sep 16, 4:14 pm, matehat wrote:
> Oh, and trying to make the url resolving mechanism look in the
> database is really a bad idea because it would trigger a bunch of
> database queries every time a request is processed by your
> application, which would really slow things down.
What do you mea
On Sep 16, 4:11 pm, matehat wrote:
> Hi,
>
> If the url only depends on the object's id (which I suppose don't
> change with time),
The only problem is, it doesn't :-) We'd like to be able to handle
redirects.
E.g. category "wine" is renamed to "wines", but we still want to be
able to redirect b
Oh, and trying to make the url resolving mechanism look in the
database is really a bad idea because it would trigger a bunch of
database queries every time a request is processed by your
application, which would really slow things down.
mathieu
On 16 sep, 10:11, matehat wrote:
> Hi,
>
> If the
Hi,
If the url only depends on the object's id (which I suppose don't
change with time), you should not have it put in the database at
first, because the object's id alone takes care of its persistence.
Then, plugging it into Django's url resolving mechanism becomes really
easy with the well-docu
Hello,
I am having little difficulties with django url system and I hope
someone can clear it up. Here's what I want to achieve: we're going to
have a tree-based catalog in our app and we'd like to index it like
this: name1/name2/name3/... I've created a database lookup table url <-
> id with urls
