wow, it works!
BiG thanks to Rudolph, you've been a great help!
- Eric
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To un
Wilson Miner wrote:
>To use the tutorial app as an example, if you have a number of choices
>for each poll, you may want to make the choices orderable by an
>arbitrary index within the poll, rather than sorting them
>alphabetically. In that case you could set order_with_respect_to =
>'poll_id' in
On 4/26/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
>
> Hi.
> I did something similar to this a while back
> I did it via a template tag.
> you can read about it here:
> http://feh.holsman.net/articles/2006/03/08/cross-tab-tag
>
Ian,
I managed to get what I wanted with the method Malcom suggested
To use the tutorial app as an example, if you have a number of choices
for each poll, you may want to make the choices orderable by an
arbitrary index within the poll, rather than sorting them
alphabetically. In that case you could set order_with_respect_to =
'poll_id' in your choices model.
On 4
Being not native English speaker I can't really get the purpose or
order_with_respect_to just by reading docs. Looking at how it's
implemented I see that related objects get some sort index unique within
one parent record and can be ordered in creation order. But why it is
needed? Can someone
On 4/25/06, Ken Kennedy <[EMAIL PROTECTED]> wrote:
I'd say put 'em there!Done---Clint Ecker[EMAIL PROTECTED]http://phaedo.cx
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group,
There was already a bug report on this, and a simple patch:http://code.djangoproject.com/ticket/1677On 4/26/06,
Rudolph <[EMAIL PROTECTED]> wrote:
This revision also causes another minor bug. When running syncdb ittells youAdding permission ''for every permission. This is caused by the __repr__ an
I think your problem is not with the comments app. Have look at the
problem + solution over here:
http://groups.google.com/group/django-users/browse_thread/thread/7d062b3cac57e4b4
Rudolph
--~--~-~--~~~---~--~~
You received this message because you are subscribed
This revision also causes another minor bug. When running syncdb it
tells you
Adding permission ''
for every permission. This is caused by the __repr__ and __str__
changes. Shall I file a bug report?
--~--~-~--~~~---~--~~
You received this message because you are
OK, I found the problem...
The problem is that manipulators don't look for the default value of the
field if the field isn't set as editable=False, which is bad because I
may (I have) objects that can be created by different users, and not all
users can set all attributes. When some group of u
Good morning,On 4/25/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
I don't know what you mean with "stop". I think each validator will beexecuted, but they will take into account whether record_type has theright value.Anyway, I personally give up :-(
You can try to find out what's happening:- crea
11 matches
Mail list logo
