#django

the django docs are very well organised... it shouldn't take much effort to find what you need

AND... it will get you more familiar with what's available

Is right. how about the performance penalty on annotate?

In the manage.py shell it was fast, well i will implement it and test

subbero: I think by the time you reach any performance penalty fron using it, you'll know that adding an index to Image.date will be the way to fix it :)

Yes, must evaluate which index now are most important. As it now changes somewhat so that other indexes are not so good anymore

subbero: how many images/categories are you talking?

But with python-django-south all i easy

Not very much

10? 100? 1000?

Less than 50 categorys

fewer than 50 categories... and how many images?

115 Images lol

total? or per category?

13 CAT

total

huh?

115 Images total, 13 cat total

Is ok, it is only that i am running on a intel atom, but the site is also not a heavy load site

Before i migrated to that intel atom i was using a via eden, there the performance on django was very bad

index won't help with that few items

Yes

which DBMS?

Just to be right. Wrong indexes also can cause weird stuff :)

On way more data for sure :)

I am currently only having the problem that some categorys have names like "FooEvent - 2006", "FooEvent - 2010" and as i had initially put in the images now those are not in order :)

Changing the date of the added dates in the database would fix it

When you "update" a record using the admin module, it actually deletes the original record and insert a new one with the same id, right?

what is a routing_key? and how is it diffrent than a queue? in celery

asarch: no, it updates it...

asarch: as in, overwrites it

I thought it deletes and recreates because PostgreSQL database say it need a "vacuum operation" :-(

asarch: well, that's an implementation detail...

Django does an UPDATE... PG does that by creating a new record, then retiring the old one

Oh

also, PGs autovacuum daemon should keep things tidy for you

I was about to blame Django for that

nope

it's nothing bad... it simply is

Thank you FunkyBob

Thank you very much for your help :-)

(also, many DBMSs work similary... and need vacuuming occasionally)

I see

Since my first approach with Django was with a SQLite3 database

think of it as defraging their data files

I was worried for my data

sqlite has a vacuum, too

Really?

Wow

as I said, most of the time it's just defragmenting their data files... since data are added/removed/resized/etc over time

we had a table where we deleted 16million old records... stayed huge, even with autovacuum [because it won't move records to other pages]

did a full vacuum, removed a metric arseload of space :P

Wow

And I was worried for my 245 entries :P

Wrong button

Should request be available in templates if I use TemplateView?

heedly: context processor?

yep