Mailing-List: contact user-help@bloodhound.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@bloodhound.apache.org
Received-SPF: pass (nike.apache.org: domain of tisdall@gmail.com designates
 209.85.217.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CA+BGpn8C+XXYzdW4d_=CjCSvbtqnt2sKs_SA=gY0Vt1ysNb42Q@mail.gmail.com>
References: 
 <CAGxYWpanwKs+4JjjwPVpJRp3zrwjyS6bjuPFn2qURf5XHRpNMQ@mail.gmail.com>
	<CA+BGpn8C+XXYzdW4d_=CjCSvbtqnt2sKs_SA=gY0Vt1ysNb42Q@mail.gmail.com>
Date: Thu, 26 Mar 2015 13:10:08 -0400
Message-ID: 
 <CAGxYWpZ8JsDQkmy=Z8AdW4HUpUp_rv2+8ER08sZ=LpXUCKHf3w@mail.gmail.com>
Subject: Re: /products page error
From: Tim Tisdall <tisdall@gmail.com>
To: user@bloodhound.apache.org
Content-Type: text/plain; charset=UTF-8

That didn't seem to have made a difference.  Where would the logging
messages appear?

I think I figured it out, though...

mysql> select * from bloodhound_productconfig where option='whut';
ERROR 1064 (42000): You have an error in your SQL syntax; check the
manual that corresponds to your MySQL server version for the right
syntax to use near 'option='whut'' at line 1
mysql> select * from bloodhound_productconfig where `option`='whut';
Empty set (0.00 sec)

mysql> select * from bloodhound_productconfig where
bloodhound_productconfig.option='whut';
Empty set (0.00 sec)


It seems the "option" part is a keyword or something in mysql and
needs to be properly escaped or qualified.  Seems like an easy
patch...


On Thu, Mar 26, 2015 at 12:58 PM, Ryan J Ollos <rjollos@apache.org> wrote:
> On Thu, Mar 26, 2015 at 9:56 AM, Tim Tisdall <tisdall@gmail.com> wrote:
>>
>> After upgrading from 0.7 to 0.8 my /products page says:
>>
>> ProgrammingError: (1064, "You have an error in your SQL syntax; check
>> the manual that corresponds to your MySQL server version for the right
>> syntax to use near 'option='icon'' at line 3")
>>
>> After many many many tries on the demo site I managed to get that page
>> to load with no issue, so I suspect there's something not right with
>> just my environment.
>>
>> Unfortunately I'm not sure how to get the whole SQL query but it
>> starts with "\n SELECT product, value FROM
>> bloodhound_productconfig\n".
>
>
> Setting [trac] debug_sql = true might provide more info.
>
> http://trac.edgewall.org/wiki/TracIni#trac-section