This query is generated in both reviews/managers.py and
reviews/datagrids.py. In these cases, it's raw SQL, so you should be able to
easily modify that.
Preferably, we'd move away from raw SQL now that Django has support for F()
expressions (things like field_name = field_name + 1 and stuff, which it
couldn't do before). But a quick fix would be to just do the = 1 on those
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Mon, Oct 18, 2010 at 8:01 AM, Mohammed Abouzour [Sybase] <
> I am trying to upgrade our RB from 1.0rc3 to 1.5. We are running on
> top of a SQLAnywhere database server. I got the database upgraded
> successfully, but when I try to access the site it gives me errors
> regarding badly generated SQL queries. The problem is with the
> reviews_review.public field. This field is a Boolean field. The query
> that is generated by RB looks as follows:
> SELECT COUNT(*) FROM reviews_review, ... WHERE reviews_review.public
> AND ...
> In the SQLAnywhere Django driver, Boolean fields are mapped to BIT
> fields on the database side. As such, the correct query above should
> have been
> SELECT COUNT(*) FROM reviews_review, ... WHERE reviews_review.public =
> 1 AND ...
> I am inheriting this system so I am still learning both Django and RB.
> What component is responsible for
> generating the correct syntax for Boolean fields?
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at