bret at pectopah
Apr 22, 2011, 11:52 AM
Post #3 of 6
I've seen this myself, on a 2.0.1 install using templates from the 1.10
Re: SQL error: invalid input syntax for type boolean
[In reply to]
series. Here's how to make it happen:
1. Get a template that creates subelements. (The old
image_resize_and_relate, for example.)
2. From the story profile, trigger a preview, which should create one or
more subelements in the current story. Note that these subelements will
not appear in the UI, because there's no mechanism for updating it if
something happens during preview.
3. Attempt a save or a save and stay. You'll see the error.
What's happening, I think, is that the form submitted by the save does
not contain any information about the new subelements, so there's
nothing passed for the "displayed" field, and that bangs into the
If you run do almost the same thing, but trigger the preview from your
workspace or a desk, the subelements get created cleanly and are present
when you go back into the story profile.
My approach was to hide: I just make the thumbnail images themselves
with find_or_create_alternate(), but no longer bother relating them to
the uploaded image container.
The ideal would be to have the preview process finish by refreshing the
story profile update itself, I suppose. AJAXers, would that be hard?
On Fri, 2011-04-22 at 10:02 -0700, David E. Wheeler wrote:
> On Apr 21, 2011, at 1:21 PM, Nick Legg wrote:
> > Has anyone seen an error like the one below? The element_type__id = 1251 is our "Thumbnail" element which is essentially just a container for a Related Media. I'm guessing, if I read this error correctly, the problem is because some code somewhere is attempting to set "displayed" to "" (empty string) where it should be a boolean. Any ideas?
> > Thanks,
> > Nick
> > [Thu Apr 21 18:47:45 2011] [error] [client 220.127.116.11] Unable to execute SQL statement: DBD::Pg::st execute failed: ERROR: invalid input syntax for type boolean: "" [.for Statement "\n UPDATE story_element\n SET element_type__id = ?, object_instance_id = ?, parent_id = ?, place = ?, object_order = ?, displayed = ?, related_story__id = ?, related_media__id = ?, active = ?\n WHERE id = ?\n " with ParamValues: 1='1251', 2='162196', 3='1773753', 4='0', 5='1', 6='', 7=undef, 8='54977', 9='1', 10='1773754'] at /usr/local/bricolage/lib/Bric/Util/DBI.pm line 1138, <GEN128> line 19983.\n, referer:https://freestyle.denison.edu/workflow/profile/story/24387
> The `displayed` column is a boolean column. The value specified for it should be either '1' or '0' (with the quotation marks, they must be strings). The value passed here, however, is an empty string ( 6='').
> Can you replicate this error? It's clearly a bug.
Pectopah Productions Inc.
bret [at] pectopah