Re: "get next" and "get last" on any field?

2008-04-07 Thread SlowLearner
ects.filter(id__lt=newsid).order_by('id')[:1] > > 2008/4/5, SlowLearner <[EMAIL PROTECTED]>: > > > > > Hi, I am hoping there is a better solution to my problem than the one > > I have come up with, or one built in to the django models. > > > I would lik

"get next" and "get last" on any field?

2008-04-05 Thread SlowLearner
Hi, I am hoping there is a better solution to my problem than the one I have come up with, or one built in to the django models. I would like to include "get next" and "get last" buttons on my view. The catch is that I want to do get next, get last on an integer field (which is not a primary key

Re: Postgres and Fixtures

2008-04-05 Thread SlowLearner
> > Thanks, I'll give that a go next time I reload the database. I tried it and it complained that sequencereset was not a valid option. However, looking in the help there is a 'sqlsequencereset' option. Running: ./manage.py sqlsequencereset Brought up a list of the setval commands to run to

Re: Postgres and Fixtures

2008-03-27 Thread SlowLearner
On Mar 27, 3:23 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > > It will run automatically if you are using trunk Django, but not if > you are using the 0.96 release. If you are using 0.96, and can't > update to trunk, you will need to run ./manage.py sequencereset after > loading a fixtur

Postgres and Fixtures

2008-03-24 Thread SlowLearner
Hi all, It looks like this problem has been fixed in the past but I have been having it crop up recently. Here is what I did: 1. created an app 2. manually entered some data 3. took a fixture dump of the app 4. dropped and created a new database 5. restored the fixture dump 6. Whenever I tried t