False alarm. Those aren't duplicate entries, they're unique entries in 
response to the same comment.

Back to square 1.



On Friday, October 12, 2012 9:43:38 AM UTC-7, Steve wrote:
>
> I think I found the offending db entry 
>
> mysql> select * from reviews_review where id=49901 \G
>
> <snip>
>
> *************************** 19. row ***************************
>                      id: 183820
>       review_request_id: 49901
>                 user_id: 439
>               timestamp: 2012-10-11 14:06:11
>                  public: 0
>                 ship_it: 0
>        base_reply_to_id: 183574
>        email_message_id: NULL
>            time_emailed: NULL
>                body_top: I think I got em.
>             body_bottom:
>    body_top_reply_to_id: 183574
> body_bottom_reply_to_id: NULL
>     reviewed_diffset_id: NULL
> *************************** 20. row ***************************
>                      id: 183821
>       review_request_id: 49901
>                 user_id: 439
>               timestamp: 2012-10-11 14:06:11
>                  public: 0
>                 ship_it: 0
>        base_reply_to_id: 183574
>        email_message_id: NULL
>            time_emailed: NULL
>                body_top:
>             body_bottom:
>    body_top_reply_to_id: NULL
> body_bottom_reply_to_id: NULL
>     reviewed_diffset_id: NULL
>
> Both of those have the same base_reply_id number, the one I keep seeing in 
> the stack trace.
>
> The million dollar question - can I safely delete the second of those 
> entries, or will that cause me no end of trouble?
>
> --Steve
>
>
> On Friday, October 12, 2012 8:47:52 AM UTC-7, Steve wrote:
>>
>> I have a user who has a review which has been ongoing for several days 
>> with numerous comments. Yesterday when he tried to add another comment he 
>> received an error page from review board. The error message in the log is:
>>
>> MultipleObjectsReturned: get() returned more than one Review -- it 
>> returned 2! Lookup parameters were {'base_reply_to': <Review: Review of 
>> 'xxxxx'>, 'user': <User: xxxxx>, 'public': False}
>>
>>
>> I'm able to access the review and make comments, as is everyone else on 
>> the review, but the user can't. He has tried 2 different browsers, cleared 
>> his browser cache and even rebooted his machine. I don't know which table 
>> in the db that query is looking in, put the review is public.  The mod 
>> python request is:
>>
>> 'PATH_INFO': 
>> u'/api/json/reviewrequests/49901/reviews/183574/replies/draft/discard/'
>>
>> Which seems odd, because that's not the only action he's attempting, but 
>> he keeps getting that error, as if the request is somehow cached.
>>
>> I'm at a loss as to how to proceed. There's been so much activity on this 
>> review that abandoning it would be a last resort. Can anyone point me in a 
>> direction that might help me to fix this?
>>
>> --Steve
>>
>>

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~----------~----~----~----~------~----~------~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Reply via email to