On 10/27/06, Waylan Limberg <[EMAIL PROTECTED]> wrote:
>
> I couldn't help but notice that in your example, it is also sorted by
> Sink *descending*. What happens if you click on "Sink" again? If I'm
> not mistaken, it should sort *ascending*. Then again, this just may be
> a coincidence of a poor
On 10/26/06, John Lenton <[EMAIL PROTECTED]> wrote:
>
[snip]
>
> this is as expected; but if you click on "Sink", you get
>
> Source | Sink v
> Anode | Cnode
> Cnode | Bnode
> Mnode | Anode
> Xnode | Anode
>
> i.e., it still sorts by Source instead of Sink. Is this a bug in
> django, or am I f
On 10/26/06, Guillermo Fernandez Castellanos
<[EMAIL PROTECTED]> wrote:
>
> Cheers,
>
> have a look at the Meta options order_with_respect_to and ordering:
> http://www.djangoproject.com/documentation/model_api/#order-with-respect-to
no, that's not it. Or I didn't understand how to use it; at any
Cheers,
have a look at the Meta options order_with_respect_to and ordering:
http://www.djangoproject.com/documentation/model_api/#order-with-respect-to
Hope it helps,
G
On 10/24/06, John Lenton <[EMAIL PROTECTED]> wrote:
>
> Hi all.
> I've got an app where I have a table of nodes, and a table
Hi all.
I've got an app where I have a table of nodes, and a table of directed
edges between those nodes. I.e,
-8<--
class Node(models.Model):
name = models.CharField(maxlength=20, core=True, blank=False)
def __str__(self):
return self.name
class Admin:
pass
clas
5 matches
Mail list logo