Mailing List Archive: The return of mysql 'precision' errors... buh-buh-buhm!

The return of mysql 'precision' errors... buh-buh-buhm!

Mar 22, 2011, 5:08 AM

Post #1 of 9 (4599 views)

Hiya,

So I spent the last week or so producing an EC2 image of Bricolage-2.0.1,
PHP 5.2.6, PHP::Interpreter and Apache 2.2.17, with mod_perl and ssl, and I
am *loving it*.

Except... in spite of the fact I'm pretty much up-to-date with everything
and anything, I'm suddenly plagued with the return of "precision" =
'precision', which looks like it was fixed years ago.

Surely there must be other EC2 users using Bric with RDS -- am I the only
one in this boat? If so, any suggestions on what settings I must have
messed up to be inflicted with this long-forgotten misery?

Cheers,
-- Todd

DBD::mysql::st execute failed: 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 '"precision" = 'precision', cols = '40', rows
= '4', length = '0', vals = '', mul' at line 1 [for Statement "UPDATE
field_type SET element_type__id = ?, name = ?, key_name = ?,
description = ?, place = ?, min_occurrence = ?, max_occurrence = ?,
autopopulated = ?, max_length = ?, sql_type = ?, widget_type = ?,
"precision" = ?, cols = ?, rows = ?, length = ?, vals = ?, multiple =
?, default_val = ?, active = ? WHERE id=?" with ParamValues: 0='1',
1='Deck', 2='deck', 3='A one-sentence teaser or subhead.', 4='1',
5='1', 6='1', 7='0', 8='256', 9='short', 10='textarea',
11='precision', 12='40', 13='4', 14='0', 15='', 16='0', 17='', 18='1',
19='12'] at /usr/local/bricolage/lib/Bric/Util/DBI.pm line 1138,
<GEN339> line 141.

Re: The return of mysql 'precision' errors... buh-buh-buhm! [ In reply to ]

david at kineticode

Mar 23, 2011, 9:13 AM

Post #2 of 9 (4507 views)

Permalink

On Mar 22, 2011, at 8:08 AM, Todd Stumpf wrote:

> So I spent the last week or so producing an EC2 image of Bricolage-2.0.1,
> PHP 5.2.6, PHP::Interpreter and Apache 2.2.17, with mod_perl and ssl, and I
> am *loving it*.

Wow. That sounds pretty insanely cool.

> Except... in spite of the fact I'm pretty much up-to-date with everything
> and anything, I'm suddenly plagued with the return of "precision" =
> 'precision', which looks like it was fixed years ago.
>
> Surely there must be other EC2 users using Bric with RDS -- am I the only
> one in this boat? If so, any suggestions on what settings I must have
> messed up to be inflicted with this long-forgotten misery?

Question: Why MySQL? Support for it is rather experimental (although I guess our docs don't say that).

> DBD::mysql::st execute failed: 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 '"precision" = 'precision', cols = '40', rows
> = '4', length = '0', vals = '', mul' at line 1 [for Statement "UPDATE
> field_type SET element_type__id = ?, name = ?, key_name = ?,
> description = ?, place = ?, min_occurrence = ?, max_occurrence = ?,
> autopopulated = ?, max_length = ?, sql_type = ?, widget_type = ?,
> "precision" = ?, cols = ?, rows = ?, length = ?, vals = ?, multiple =
> ?, default_val = ?, active = ? WHERE id=?" with ParamValues: 0='1',
> 1='Deck', 2='deck', 3='A one-sentence teaser or subhead.', 4='1',
> 5='1', 6='1', 7='0', 8='256', 9='short', 10='textarea',
> 11='precision', 12='40', 13='4', 14='0', 15='', 16='0', 17='', 18='1',
> 19='12'] at /usr/local/bricolage/lib/Bric/Util/DBI.pm line 1138,
> <GEN339> line 141.

I'm guessing that for some reason ANSII support isn't enabled, so it doesn't recognize the double-quotes as quoting an identifier. What version of DBI do you have? Make sure that the callback on line s 57-67 in lib/Bric/Util/DBD/mysql.pm is called on connection.

Best,

David

Re: The return of mysql 'precision' errors... buh-buh-buhm! [ In reply to ]

tds at nineatatime

Mar 24, 2011, 3:10 AM

Post #3 of 9 (4500 views)

Permalink

Update on this: I realized that this had to be an operational problem, not
an initialization problem..

I had been able to make Element Type changes earlier, which means this had
to have worked for a bit, but had since gone sour.

To make sure I wasn't inventing memories, I bounced the server. Things
worked just fine without any other changes...

Because I'm using RDS, I'm wondering if it might not be a flaw in their db
virtualization -- perhaps they moved the connection from A to B, but lost
the ansi setting for the connection...

As to why MySQL, it was just because that's the only thing RDS supports
right now. I'm mostly doing this to see how far along I can get on a total
AWS-based turnkey solution.

If there is a way to get a managed Postgresql installation on AWS (it looked
like you had to spin up your own db instance if you want Postgresql) I'd
happily switch...

-- Todd

On Wed, Mar 23, 2011 at 9:13 AM, David E. Wheeler <david@kineticode.com>wrote:

> On Mar 22, 2011, at 8:08 AM, Todd Stumpf wrote:
>
> > So I spent the last week or so producing an EC2 image of Bricolage-2.0.1,
> > PHP 5.2.6, PHP::Interpreter and Apache 2.2.17, with mod_perl and ssl, and
> I
> > am *loving it*.
>
> Wow. That sounds pretty insanely cool.
>
> > Except... in spite of the fact I'm pretty much up-to-date with everything
> > and anything, I'm suddenly plagued with the return of "precision" =
> > 'precision', which looks like it was fixed years ago.
> >
> > Surely there must be other EC2 users using Bric with RDS -- am I the only
> > one in this boat? If so, any suggestions on what settings I must have
> > messed up to be inflicted with this long-forgotten misery?
>
> Question: Why MySQL? Support for it is rather experimental (although I
> guess our docs don't say that).
>
> > DBD::mysql::st execute failed: 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 '"precision" = 'precision', cols = '40', rows
> > = '4', length = '0', vals = '', mul' at line 1 [for Statement "UPDATE
> > field_type SET element_type__id = ?, name = ?, key_name = ?,
> > description = ?, place = ?, min_occurrence = ?, max_occurrence = ?,
> > autopopulated = ?, max_length = ?, sql_type = ?, widget_type = ?,
> > "precision" = ?, cols = ?, rows = ?, length = ?, vals = ?, multiple =
> > ?, default_val = ?, active = ? WHERE id=?" with ParamValues: 0='1',
> > 1='Deck', 2='deck', 3='A one-sentence teaser or subhead.', 4='1',
> > 5='1', 6='1', 7='0', 8='256', 9='short', 10='textarea',
> > 11='precision', 12='40', 13='4', 14='0', 15='', 16='0', 17='', 18='1',
> > 19='12'] at /usr/local/bricolage/lib/Bric/Util/DBI.pm line 1138,
> > <GEN339> line 141.
>
> I'm guessing that for some reason ANSII support isn't enabled, so it
> doesn't recognize the double-quotes as quoting an identifier. What version
> of DBI do you have? Make sure that the callback on line s 57-67 in
> lib/Bric/Util/DBD/mysql.pm is called on connection.
>
> Best,
>
> David
>
>

Re: The return of mysql 'precision' errors... buh-buh-buhm! [ In reply to ]

david at kineticode

Mar 24, 2011, 7:01 AM

Post #4 of 9 (4507 views)

Permalink

On Mar 24, 2011, at 6:10 AM, Todd Stumpf wrote:

> Because I'm using RDS, I'm wondering if it might not be a flaw in their db
> virtualization -- perhaps they moved the connection from A to B, but lost
> the ansi setting for the connection...

Oh, you might get this problem if AWS is using connection pooling or something.

> As to why MySQL, it was just because that's the only thing RDS supports
> right now. I'm mostly doing this to see how far along I can get on a total
> AWS-based turnkey solution.

Gotcha.

> If there is a way to get a managed Postgresql installation on AWS (it looked
> like you had to spin up your own db instance if you want Postgresql) I'd
> happily switch...

Can you tweak your my.cnf settings? If so, use this:

http://justatheory.com/computers/databases/mysql/configuration.html

And if anything in Bric::Util::DBD::mysql isn't in that recipe, put the missing stuff in, too.

Best,

David

RE: The return of mysql 'precision' errors... buh-buh-buhm! [ In reply to ]

adam at RFXTechnologies

Apr 5, 2011, 12:21 PM

Post #5 of 9 (4472 views)

Permalink

Todd,
Have you continued to have issues with the DB connection? I would really like to do this also, but not if it doesn't work.

Adam

> -----Original Message-----
> [mailto:users@lists.bricolagecms.org] On Behalf Of Todd Stumpf
> Sent: Thursday, March 24, 2011 6:11 AM

> Because I'm using RDS, I'm wondering if it might not be a flaw in their
> db virtualization -- perhaps they moved the connection from A to B, but
> lost the ansi setting for the connection...
>
> -- Todd

Re: The return of mysql 'precision' errors... buh-buh-buhm! [ In reply to ]

tds at nineatatime

Apr 7, 2011, 1:47 AM

Post #6 of 9 (4455 views)

Permalink

I've located the proper EC2 magic to tweak the mysql server settings,
but I haven't actually done it yet. It happens so rarely that a
server restart is less stress than turning magic dials that may or may
not eat my data.

I will give adjusting the settings a try this weekend, after the
weekly back-up, and let you know if that solves/destroys everything.

-- Todd

On Tue, Apr 5, 2011 at 12:21 PM, Adam Wilson <adam@rfxtechnologies.com> wrote:
> Todd,
> Have you continued to have issues with the DB connection? I would really like to do this also, but not if it doesn't work.
>
> Adam
>
>> -----Original Message-----
>> [mailto:users@lists.bricolagecms.org] On Behalf Of Todd Stumpf
>> Sent: Thursday, March 24, 2011 6:11 AM
>
>> Because I'm using RDS, I'm wondering if it might not be a flaw in their
>> db virtualization -- perhaps they moved the connection from A to B, but
>> lost the ansi setting for the connection...
>>
>> -- Todd
>

Re: The return of mysql 'precision' errors... buh-buh-buhm! [ In reply to ]

tds at nineatatime

Apr 19, 2011, 1:17 AM

Post #7 of 9 (4417 views)

Permalink

Meh.

The EC2 magic isn't quite magical enough ... it doesn't (or at least I
can't seem to be able to get it to) support multiple option values at
the same time. You can set multiple options, but each option can only
have one value, not a set of values.

Maybe I'm just spelling things wrong, but I think its a limitation in
the way they parse options ... commas are just welcome.

So, anyways, I've set the sql_mode to ansi, and I'll see if that keeps
me from needing to reboot.

Cheers,
-- Todd

On Thu, Apr 7, 2011 at 1:47 AM, Todd Stumpf <tds@nineatatime.net> wrote:
> I've located the proper EC2 magic to tweak the mysql server settings,
> but I haven't actually done it yet. It happens so rarely that a
> server restart is less stress than turning magic dials that may or may
> not eat my data.
>
> I will give adjusting the settings a try this weekend, after the
> weekly back-up, and let you know if that solves/destroys everything.
>
> -- Todd
>
> On Tue, Apr 5, 2011 at 12:21 PM, Adam Wilson <adam@rfxtechnologies.com> wrote:
>> Todd,
>> Have you continued to have issues with the DB connection? I would really like to do this also, but not if it doesn't work.
>>
>> Adam
>>
>>> -----Original Message-----
>>> [mailto:users@lists.bricolagecms.org] On Behalf Of Todd Stumpf
>>> Sent: Thursday, March 24, 2011 6:11 AM
>>
>>> Because I'm using RDS, I'm wondering if it might not be a flaw in their
>>> db virtualization -- perhaps they moved the connection from A to B, but
>>> lost the ansi setting for the connection...
>>>
>>> -- Todd
>>
>

RE: The return of mysql 'precision' errors... buh-buh-buhm! [ In reply to ]

adam at RFXTechnologies

May 5, 2011, 2:51 PM

Post #8 of 9 (4373 views)

Permalink

Todd,
Had any issues with this since setting sql_mode to ansi?
If not, would you be willing to share your configurations with me so that I can create a similar environment? I have not tried before, but if I can get it to work, I will create an Amazon image so that it can be leveraged by future generations.

Adam

> -----Original Message-----
> From: users@lists.bricolagecms.org [mailto:users@lists.bricolagecms.org] On
> Behalf Of Todd Stumpf
> Sent: Tuesday, April 19, 2011 4:18 AM
> To: users@lists.bricolagecms.org
> Subject: Re: The return of mysql 'precision' errors... buh-buh-buhm!
>
> Meh.
>
> The EC2 magic isn't quite magical enough ... it doesn't (or at least I can't seem
> to be able to get it to) support multiple option values at the same time. You
> can set multiple options, but each option can only have one value, not a set
> of values.
>
> Maybe I'm just spelling things wrong, but I think its a limitation in the way
> they parse options ... commas are just welcome.
>
> So, anyways, I've set the sql_mode to ansi, and I'll see if that keeps me from
> needing to reboot.
>
> Cheers,
> -- Todd
>
> On Thu, Apr 7, 2011 at 1:47 AM, Todd Stumpf <tds@nineatatime.net> wrote:
> > I've located the proper EC2 magic to tweak the mysql server settings,
> > but I haven't actually done it yet. It happens so rarely that a
> > server restart is less stress than turning magic dials that may or may
> > not eat my data.
> >
> > I will give adjusting the settings a try this weekend, after the
> > weekly back-up, and let you know if that solves/destroys everything.
> >
> > -- Todd
> >
> > On Tue, Apr 5, 2011 at 12:21 PM, Adam Wilson
> <adam@rfxtechnologies.com> wrote:
> >> Todd,
> >> Have you continued to have issues with the DB connection? I would
> really like to do this also, but not if it doesn't work.
> >>
> >> Adam
> >>
> >>> -----Original Message-----
> >>> [mailto:users@lists.bricolagecms.org] On Behalf Of Todd Stumpf
> >>> Sent: Thursday, March 24, 2011 6:11 AM
> >>
> >>> Because I'm using RDS, I'm wondering if it might not be a flaw in
> >>> their db virtualization -- perhaps they moved the connection from A
> >>> to B, but lost the ansi setting for the connection...
> >>>
> >>> -- Todd
> >>
> >

Re: The return of mysql 'precision' errors... buh-buh-buhm! [ In reply to ]

ps at phillipadsmith

May 6, 2011, 10:08 AM

Post #9 of 9 (4357 views)

Permalink

I'm also curious what would be required to get Bricolage running on some of the new PaaS (or Camel-as-a-Service) offerings: http://ps.ht/iUVAtz

Phillip.

On 2011-05-05, at 5:51 PM, Adam Wilson wrote:

> Todd,
> Had any issues with this since setting sql_mode to ansi?
> If not, would you be willing to share your configurations with me so that I can create a similar environment? I have not tried before, but if I can get it to work, I will create an Amazon image so that it can be leveraged by future generations.
>
> Adam
>
>> -----Original Message-----
>> From: users@lists.bricolagecms.org [mailto:users@lists.bricolagecms.org] On
>> Behalf Of Todd Stumpf
>> Sent: Tuesday, April 19, 2011 4:18 AM
>> To: users@lists.bricolagecms.org
>> Subject: Re: The return of mysql 'precision' errors... buh-buh-buhm!
>>
>> Meh.
>>
>> The EC2 magic isn't quite magical enough ... it doesn't (or at least I can't seem
>> to be able to get it to) support multiple option values at the same time. You
>> can set multiple options, but each option can only have one value, not a set
>> of values.
>>
>> Maybe I'm just spelling things wrong, but I think its a limitation in the way
>> they parse options ... commas are just welcome.
>>
>> So, anyways, I've set the sql_mode to ansi, and I'll see if that keeps me from
>> needing to reboot.
>>
>> Cheers,
>> -- Todd
>>
>> On Thu, Apr 7, 2011 at 1:47 AM, Todd Stumpf <tds@nineatatime.net> wrote:
>>> I've located the proper EC2 magic to tweak the mysql server settings,
>>> but I haven't actually done it yet. It happens so rarely that a
>>> server restart is less stress than turning magic dials that may or may
>>> not eat my data.
>>>
>>> I will give adjusting the settings a try this weekend, after the
>>> weekly back-up, and let you know if that solves/destroys everything.
>>>
>>> -- Todd
>>>
>>> On Tue, Apr 5, 2011 at 12:21 PM, Adam Wilson
>> <adam@rfxtechnologies.com> wrote:
>>>> Todd,
>>>> Have you continued to have issues with the DB connection? I would
>> really like to do this also, but not if it doesn't work.
>>>>
>>>> Adam
>>>>
>>>>> -----Original Message-----
>>>>> [mailto:users@lists.bricolagecms.org] On Behalf Of Todd Stumpf
>>>>> Sent: Thursday, March 24, 2011 6:11 AM
>>>>
>>>>> Because I'm using RDS, I'm wondering if it might not be a flaw in
>>>>> their db virtualization -- perhaps they moved the connection from A
>>>>> to B, but lost the ansi setting for the connection...
>>>>>
>>>>> -- Todd
>>>>
>>>