tds at nineatatime
Mar 24, 2011, 3:10 AM
Post #3 of 9
Update on this: I realized that this had to be an operational problem, not
Re: The return of mysql 'precision' errors... buh-buh-buhm!
[In reply to]
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
On Wed, Mar 23, 2011 at 9:13 AM, David E. Wheeler <david [at] kineticode>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
> > 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.