Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Bricolage>
  3. devel
Upgrade 1.10.6 -> 1.11.2
rolfm at denison
Jun 18, 2009, 7:06 AM
Post #1 of 12 (8010 views)
Permalink
So I've been upgrading. System now runs, I have access to groups,
elements permissions, etc. However, any time I try to get to a screen
with stories, I get an error like this:

[Thu Jun 18 14:00:40 2009] [error] [client 140.141.15.6] Unable to
execute SQL statement: DBD::Pg::st execute failed: ERROR: function
group_concat(integer) does not exist\nLINE 2: ..._id, i.slug,
i.cover_date, i.note, i.checked_out, group_conc...
\n ^
\nHINT: No function matches the given name and argument types. You
might need to add explicit type casts. [for Statement "\n SELECT
s.id, s.uuid, s.priority, s.source__id, s.usr__id, s.element_type__id,
s.first_publish_date, s.publish_date, s.expire_date,
s.current_version, s.published_version, s.workflow__id,
s.publish_status, s.primary_uri, s.active, s.desk__id, s.site__id,
s.alias_id, i.id, i.name, i.description, i.story__id, i.version,
i.usr__id, i.primary_oc__id, i.slug, i.cover_date, i.note,
i.checked_out, group_concat( DISTINCT m.grp__id ),
group_concat( DISTINCT c.asset_grp_id ), group_concat( DISTINCT
w.asset_grp_id )\n FROM story_instance i, story_member sm,
member m, story__category sc, category c, workflow w, story s , member
m2, story_member sm2\n WHERE s.id = i.story__id AND sm.object_id
= s.id AND m.id = sm.member__id AND m.active = '1' AND
sc.story_instance__id = i.id AND c.id = sc.category__id AND
s.workflow__id = w.id AND s.current_version = i.version AND
i.checked_out = ( SELECT checked_out FROM story_instance WHERE version
= i.version AND story__id = i.story__id ORDER BY checked_out DESC
LIMIT 1 ) AND s.active = ? AND m2.grp__id = ? AND m2.active = '1' AND
sm2.member__id = m2.id AND s.id = sm2.object_id\n GROUP BY s.id,
s.uuid, s.priority, s.source__id, s.usr__id, s.element_type__id,
s.first_publish_date, s.publish_date, s.expire_date,
s.current_version, s.published_version, s.workflow__id,
s.publish_status, s.primary_uri, s.active, s.desk__id, s.site__id,
s.alias_id, i.id, i.name, i.description, i.story__id, i.version,
i.usr__id, i.primary_oc__id, i.slug, i.cover_date, i.note,
i.checked_out\n ORDER BY i.cover_date, s.id\n" with ParamValues:
1='1', 2='4054'] at /usr/local/bricolage/lib/Bric/Util/DBI.pm line
1134.\n\nStack:\n [/usr/local/bricolage/lib/Bric/Util/DBI.pm:1134]\n
[/usr/local/bricolage/lib/Bric/Util/DBI.pm:758]\n [/usr/local/
bricolage/lib/Bric/Biz/Asset.pm:308]\n [/usr/local/bricolage/lib/Bric/
Util/Grp.pm:1356]\n [/usr/local/bricolage/lib/Bric/Biz/Workflow/Parts/
Desk.pm:935]\n [/usr/local/bricolage/lib/Bric/Biz/Workflow/Parts/
Desk.pm:957]\n [/usr/local/bricolage/comp/widgets/desk/desk.mc:44]\n
[/usr/local/bricolage/comp/workflow/profile/desk/dhandler:12]\n [/usr/
local/bricolage/comp/autohandler:7]\n, referer: http://wsbric1.cache.denison.edu/admin/profile/user/1029


does this mean I need to run some scripts by hand like Scott did back
here?

http://www.gossamer-threads.com/lists/bricolage/devel/36191

If so, maybe this is something that needs to be addressed in the
upgrade scripts.


Matt
Re: Upgrade 1.10.6 -> 1.11.2 [ In reply to ]
rolfm at denison
Jun 27, 2009, 4:19 PM
Post #2 of 12 (7809 views)
Permalink
Any thoughts on this?

Thanks,

Matt

On Jun 18, 2009, at 10:06 AM, Matt Rolf wrote:

> So I've been upgrading. System now runs, I have access to groups,
> elements permissions, etc. However, any time I try to get to a
> screen with stories, I get an error like this:
>
> [Thu Jun 18 14:00:40 2009] [error] [client 140.141.15.6] Unable to
> execute SQL statement: DBD::Pg::st execute failed: ERROR: function
> group_concat(integer) does not exist\nLINE 2: ..._id, i.slug,
> i.cover_date, i.note, i.checked_out, group_conc...
> \n ^
> \nHINT: No function matches the given name and argument types. You
> might need to add explicit type casts. [for Statement "\n
> SELECT s.id, s.uuid, s.priority, s.source__id, s.usr__id,
> s.element_type__id, s.first_publish_date, s.publish_date,
> s.expire_date, s.current_version, s.published_version,
> s.workflow__id, s.publish_status, s.primary_uri, s.active,
> s.desk__id, s.site__id, s.alias_id, i.id, i.name, i.description,
> i.story__id, i.version, i.usr__id, i.primary_oc__id, i.slug,
> i.cover_date, i.note, i.checked_out, group_concat( DISTINCT
> m.grp__id ), group_concat( DISTINCT c.asset_grp_id ),
> group_concat( DISTINCT w.asset_grp_id )\n FROM story_instance
> i, story_member sm, member m, story__category sc, category c,
> workflow w, story s , member m2, story_member sm2\n WHERE s.id
> = i.story__id AND sm.object_id = s.id AND m.id = sm.member__id AND
> m.active = '1' AND sc.story_instance__id = i.id AND c.id =
> sc.category__id AND s.workflow__id = w.id AND s.current_version =
> i.version AND i.checked_out = ( SELECT checked_out FROM
> story_instance WHERE version = i.version AND story__id = i.story__id
> ORDER BY checked_out DESC LIMIT 1 ) AND s.active = ? AND m2.grp__id
> = ? AND m2.active = '1' AND sm2.member__id = m2.id AND s.id =
> sm2.object_id\n GROUP BY s.id, s.uuid, s.priority,
> s.source__id, s.usr__id, s.element_type__id, s.first_publish_date,
> s.publish_date, s.expire_date, s.current_version,
> s.published_version, s.workflow__id, s.publish_status,
> s.primary_uri, s.active, s.desk__id, s.site__id, s.alias_id, i.id,
> i.name, i.description, i.story__id, i.version, i.usr__id,
> i.primary_oc__id, i.slug, i.cover_date, i.note, i.checked_out\n
> ORDER BY i.cover_date, s.id\n" with ParamValues: 1='1', 2='4054']
> at /usr/local/bricolage/lib/Bric/Util/DBI.pm line 1134.\n\nStack:\n
> [/usr/local/bricolage/lib/Bric/Util/DBI.pm:1134]\n [/usr/local/
> bricolage/lib/Bric/Util/DBI.pm:758]\n [/usr/local/bricolage/lib/
> Bric/Biz/Asset.pm:308]\n [/usr/local/bricolage/lib/Bric/Util/Grp.pm:
> 1356]\n [/usr/local/bricolage/lib/Bric/Biz/Workflow/Parts/Desk.pm:
> 935]\n [/usr/local/bricolage/lib/Bric/Biz/Workflow/Parts/Desk.pm:
> 957]\n [/usr/local/bricolage/comp/widgets/desk/desk.mc:44]\n [/usr/
> local/bricolage/comp/workflow/profile/desk/dhandler:12]\n [/usr/
> local/bricolage/comp/autohandler:7]\n, referer: http://wsbric1.cache.denison.edu/admin/profile/user/1029
>
>
> does this mean I need to run some scripts by hand like Scott did
> back here?
>
> http://www.gossamer-threads.com/lists/bricolage/devel/36191
>
> If so, maybe this is something that needs to be addressed in the
> upgrade scripts.
>
>
> Matt
Re: Upgrade 1.10.6 -> 1.11.2 [ In reply to ]
david at kineticode
Jun 29, 2009, 9:43 AM
Post #3 of 12 (7808 views)
Permalink
On Jun 18, 2009, at 7:06 AM, Matt Rolf wrote:

> So I've been upgrading. System now runs, I have access to groups,
> elements permissions, etc. However, any time I try to get to a
> screen with stories, I get an error like this:
>
> [Thu Jun 18 14:00:40 2009] [error] [client 140.141.15.6] Unable to
> execute SQL statement: DBD::Pg::st execute failed: ERROR: function
> group_concat(integer) does not exist\nLINE 2: ..._id, i.slug,
> i.cover_date, i.note, i.checked_out, group_conc...\n

Sounds like you weren't properly upgraded. What do these output in psql?

\df id_list
\da group_concat

Best,

David
Re: Upgrade 1.10.6 -> 1.11.2 [ In reply to ]
rolfm at denison
Jul 9, 2009, 12:01 PM
Post #4 of 12 (7729 views)
Permalink
On Jun 29, 2009, at 12:43 PM, David E. Wheeler wrote:

> On Jun 18, 2009, at 7:06 AM, Matt Rolf wrote:
>
>> So I've been upgrading. System now runs, I have access to groups,
>> elements permissions, etc. However, any time I try to get to a
>> screen with stories, I get an error like this:
>>
>> [Thu Jun 18 14:00:40 2009] [error] [client 140.141.15.6] Unable to
>> execute SQL statement: DBD::Pg::st execute failed: ERROR: function
>> group_concat(integer) does not exist\nLINE 2: ..._id, i.slug,
>> i.cover_date, i.note, i.checked_out, group_conc...\n
>
> Sounds like you weren't properly upgraded. What do these output in
> psql?
>
> \df id_list
> \da group_concat

Nothing at all. Hmm.
Re: Upgrade 1.10.6 -> 1.11.2 [ In reply to ]
rolfm at denison
Jul 9, 2009, 12:05 PM
Post #5 of 12 (7740 views)
Permalink
On Jul 9, 2009, at 3:01 PM, Matt Rolf wrote:

>> \df id_list
>> \da group_concat
>
> Nothing at all. Hmm.
>

And actually, this matches production 1.10.6.

-Matt
Re: Upgrade 1.10.6 -> 1.11.2 [ In reply to ]
david at kineticode
Jul 9, 2009, 3:02 PM
Post #6 of 12 (7727 views)
Permalink
On Jul 9, 2009, at 12:05 PM, Matt Rolf wrote:

>>> \df id_list
>>> \da group_concat
>>
>> Nothing at all. Hmm.
>>
>
> And actually, this matches production 1.10.6.

Sounds like inst/upgrade/1.11.0/change_aggregate_name_Pg.pl didn't run
-- and possibly more of the upgrade scripts.

Best,

David
Re: Upgrade 1.10.6 -> 1.11.2 [ In reply to ]
rolfm at denison
Jul 10, 2009, 6:02 AM
Post #7 of 12 (7737 views)
Permalink
On Jul 9, 2009, at 6:02 PM, David E. Wheeler wrote:

> On Jul 9, 2009, at 12:05 PM, Matt Rolf wrote:
>
>>>> \df id_list
>>>> \da group_concat
>>>
>>> Nothing at all. Hmm.
>>>
> Sounds like inst/upgrade/1.11.0/change_aggregate_name_Pg.pl didn't
> run -- and possibly more of the upgrade scripts.

Hmm. I wonder why that might be?
Re: Upgrade 1.10.6 -> 1.11.2 [ In reply to ]
david at kineticode
Jul 10, 2009, 8:43 AM
Post #8 of 12 (7721 views)
Permalink
On Jul 10, 2009, at 6:02 AM, Matt Rolf wrote:

>> Sounds like inst/upgrade/1.11.0/change_aggregate_name_Pg.pl didn't
>> run -- and possibly more of the upgrade scripts.
>
> Hmm. I wonder why that might be?

I dunno, but if this isn't a production install, you can edit
$BRICOLAGE_ROOT/conf/install.db to set the version back to 1.10.6 and
run the upgrade again to see what happens. It should have complained
loudly if a migration failed. Could it be that it somehow thought that
the migrations had already been run, that install.db already was set
to 1.11.2?

Best,

David
Re: Upgrade 1.10.6 -> 1.11.2 [ In reply to ]
rolfm at denison
Jul 10, 2009, 11:41 AM
Post #9 of 12 (7731 views)
Permalink
On Jul 9, 2009, at 6:02 PM, David E. Wheeler wrote:

> On Jul 9, 2009, at 12:05 PM, Matt Rolf wrote:
>
>>>> \df id_list
>>>> \da group_concat
>>>
>>> Nothing at all. Hmm.
>>>
>>
>> And actually, this matches production 1.10.6.
>
> Sounds like inst/upgrade/1.11.0/change_aggregate_name_Pg.pl didn't
> run -- and possibly more of the upgrade scripts.

Now that I look at it's, it's only running scripts for the version I'm
upgrading to:

Looking for scripts for 1.11.2 in inst/upgrade/1.11.2
Running '/usr/pkg/bin/perl inst/upgrade/1.11.2/cover_date_not_null.pl'.

Or if I try the latest release that's on the web site:

Looking for scripts for 1.11.1 in inst/upgrade/1.11.1
Running '/usr/pkg/bin/perl inst/upgrade/1.11.1/add_displayed.pl'.
Re: Upgrade 1.10.6 -> 1.11.2 [ In reply to ]
david at kineticode
Jul 10, 2009, 11:52 AM
Post #10 of 12 (7726 views)
Permalink
On Jul 10, 2009, at 11:41 AM, Matt Rolf wrote:

> Now that I look at it's, it's only running scripts for the version
> I'm upgrading to:
>
> Looking for scripts for 1.11.2 in inst/upgrade/1.11.2
> Running '/usr/pkg/bin/perl inst/upgrade/1.11.2/
> cover_date_not_null.pl'.
>
> Or if I try the latest release that's on the web site:
>
> Looking for scripts for 1.11.1 in inst/upgrade/1.11.1
> Running '/usr/pkg/bin/perl inst/upgrade/1.11.1/add_displayed.pl'.

What version is in $BRICOLAGE_ROOT/conf/install.db?

Best,

David
Re: Upgrade 1.10.6 -> 1.11.2 [ In reply to ]
rolfm at denison
Jul 10, 2009, 11:55 AM
Post #11 of 12 (7706 views)
Permalink
On Jul 10, 2009, at 2:52 PM, David E. Wheeler wrote:

> On Jul 10, 2009, at 11:41 AM, Matt Rolf wrote:
>
>> Now that I look at it's, it's only running scripts for the version
>> I'm upgrading to:
>>
>> Looking for scripts for 1.11.2 in inst/upgrade/1.11.2
>> Running '/usr/pkg/bin/perl inst/upgrade/1.11.2/
>> cover_date_not_null.pl'.
>>
>> Or if I try the latest release that's on the web site:
>>
>> Looking for scripts for 1.11.1 in inst/upgrade/1.11.1
>> Running '/usr/pkg/bin/perl inst/upgrade/1.11.1/add_displayed.pl'.
>
> What version is in $BRICOLAGE_ROOT/conf/install.db?

It had been 1.10.6
Re: Upgrade 1.10.6 -> 1.11.2 [ In reply to ]
rolfm at denison
Jul 10, 2009, 12:04 PM
Post #12 of 12 (7707 views)
Permalink
On Jul 10, 2009, at 2:55 PM, Matt Rolf wrote:

Ok, when I moved the 1.11.0 and 1.11.1 upgrade scripts into the /inst/
1.11.2 directory, they ran, and the install starts up now! Yay!

Thanks for the help. It looks like if you're upgrading from 1.10.x,
it needs to know to run those.

-Matt

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal