Come to think of it... I've checked the revision that last made the
changes to the lines of
the query and even in the version from 5 years ago the predictivemodule.*
columns returned by the query never were used in the get_management_node_info(),
must be some remnants from a time long since forgotten :)

SELECT
managementnode.*,
resource.id AS resource_id,
predictivemodule.name AS predictive_name,
predictivemodule.prettyname AS predictive_prettyname,
predictivemodule.description AS predictive_description,
predictivemodule.perlpackage  AS predictive_perlpackage,

-- 
Bostjan

On Thu, Sep 25, 2014 at 5:07 PM, Aaron Peeler <[email protected]> wrote:
> ok, thanks for pointing that out. I should have that fix committed shortly.
>
> Aaron
>
>
> On Thu, Sep 25, 2014 at 10:53 AM, Bostjan Boric <[email protected]> wrote:
>> get_management_node_info() tries to perform a query which includes the
>> now removed predictivemoduleid column, making the query fail:
>>
>> utils.pm:4547-4548:
>>
>> WHERE
>> managementnode.predictivemoduleid = predictivemodule.id
>>
>> --
>> Bostjan
>>
>> On Tue, Sep 23, 2014 at 9:35 PM, Aaron Peeler <[email protected]> wrote:
>>> JFYI - I made a commit moments ago, that would break existing installs
>>> if a schema change is not also made.
>>>
>>> The changes relates to moving the predictive reload modules from the
>>> management node table to the computer table.
>>>
>>> If testing the trunk code, you will need to also update your schema.
>>>
>>> Aaron
>>>
>>> --
>>> Aaron Peeler
>>> Program Manager
>>> Virtual Computing Lab
>>> NC State University
>>>
>>> All electronic mail messages in connection with State business which
>>> are sent to or received by this account are subject to the NC Public
>>> Records Law and may be disclosed to third parties.
>
>
>
> --
> Aaron Peeler
> Program Manager
> Virtual Computing Lab
> NC State University
>
> All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.

Reply via email to