Re: Mad SELECT with the admin view.

2006-10-15 Thread Gabriel Gunderson
On 10/15/06, Karen Tracey <[EMAIL PROTECTED]> wrote: > Yah, that does look bizarre. I have no idea what is going on but am a > sucker for puzzles so tried to make some sense of the select. My > feeling is the problem isn't in the StagedOrder class that you posted > but rather one of the ones get

Re: Mad SELECT with the admin view.

2006-10-15 Thread Karen Tracey
Yah, that does look bizarre. I have no idea what is going on but am a sucker for puzzles so tried to make some sense of the select. My feeling is the problem isn't in the StagedOrder class that you posted but rather one of the ones getting pulled in as a result of the StagingArea ForeignKey. Th

Re: Mad SELECT with the admin view.

2006-10-14 Thread Gabriel Gunderson
On 10/14/06, ggundy <[EMAIL PROTECTED]> wrote: > There must be some kind of spanning or looping going on as the SELECT > is full of this type of thing: "AND "country176"."world_region_id" = > "world_region177"."id" AND "shipper169"."message_type_id" = > "message_type178"."id" AND." I thought I wo

Mad SELECT with the admin view.

2006-10-14 Thread ggundy
I'm getting an error (bubbled up from PostgreSQL) when visiting the Admin page for a table I have called "staged_order." Here is the class: *** class StagedOrder(models.Model): def __str__(self): return 'FIXME' staging_area = models.ForeignKey(StagingAr