Midgard CMS
Open Source Content Management System
Midgard Project > Discussion > User forum > DB errors on executing purge_deleted.php

DB errors on executing purge_deleted.php

  1. Andreas Flack

    DB errors on executing purge_deleted.php

    Thu March 13 2008 18:25:03 UTC
    Hi!

    I noticed that I get some DB errors while browsing Asgard trash or
    executing purge_deleted from various tables:


    Processing class org_routamc_positioning_location

    ( ! ) Warning: (pid:11452): QUERY FAILED: Unknown column
    'org_routamc_positioning_location.country' in 'field list'
    /usr/share/php/midcom/lib/midcom/exec/purge_deleted.php on line 33


    Processing class org_routamc_positioning_country

    ( ! ) Warning: (pid:11452): QUERY FAILED: Table
    'midgard.org_routamc_positioning_country' doesn't exist


    Processing class org_openpsa_expense

    ( ! ) Warning: (pid:11452): QUERY FAILED: Unknown column
    'org_openpsa_expense.revision' in 'field list'


    Processing class org_openpsa_deliverable

    ( ! ) Warning: (pid:11452): QUERY FAILED: Unknown column
    'org_openpsa_deliverable.target' in 'field list'


    Processing class org_openpsa_document_link_organization

    ( ! ) Warning: (pid:11452): QUERY FAILED: Table
    'midgard.org_openpsa_document_link' doesn't exist


    Processing class org_openpsa_products_businessarea

    ( ! ) Warning: (pid:11452): QUERY FAILED: Unknown column
    'org_openpsa_products_businessarea.created' in 'field list'


    Processing class org_openpsa_products_businessarea_member

    ( ! ) Warning: (pid:11452): QUERY FAILED: Unknown column
    'org_openpsa_products_businessarea_member.created'



    The database in question was just updated from 2.6 running on a
    different server, where none of the components in question where
    installed (so the tables are all empty and so far unused). I ran
    datagard update multiple times and have TableCreate and TableUpdate set
    to true in the config file, but this doesn't fix those problems.

    In this particular database, I can live without those tables, but I
    still wonder why some columns/tables apparently didn't get created. Also
    I wonder if the missing columns should be added to the database or
    removed from the XML schema.


    Bye,

    Andreas


    _______________________________________________
    user mailing list
    user@lists.midgard-project.org
    http://lists.midgard-project.org/mailman/listinfo/user
    •  Reply
    • stock-icons/16x16/stock_help-agent.png Report abuse
  2. Piotr Pokora

    Re: [midgard-user] DB errors on executing purge_deleted.php

    Thu March 13 2008 19:05:08 UTC
    Andreas Flack writes:
    > Hi!

    Hi!

    > The database in question was just updated from 2.6 running on a
    > different server, where none of the components in question where
    > installed (so the tables are all empty and so far unused). I ran
    > datagard update multiple times and have TableCreate and TableUpdate set
    > to true in the config file, but this doesn't fix those problems.

    TableCreate and TableUpdate are midgard-schema related.
    So set them to true and run `midgard-schema configname` instead of datagard.

    Please, update to 1.8.7 before doing this as table create/update is
    highly improved there.

    Also you can set LogLevel to 'message' before running midgard-schema.
    It will produce nice messages about what table is created/already
    exists, and what column is created/already exist.

    You can "redirect" all message from terminal to LogFile which is also
    configurable.

    Piotras
    _______________________________________________
    user mailing list
    user@lists.midgard-project.org
    http://lists.midgard-project.org/mailman/listinfo/user
    •  Reply
    • stock-icons/16x16/stock_help-agent.png Report abuse
  3. Piotr Pokora

    Re: [midgard-user] DB errors on executing purge_deleted.php

    Thu March 13 2008 20:15:02 UTC
    Andreas Flack writes:

    >> Also you can set LogLevel to 'message' before running midgard-schema.
    >> It will produce nice messages about what table is created/already
    >> exists, and what column is created/already exist.
    >
    > I had tried that before, but all I got was a memory access error. The
    > funny thing is that I tried it again now, and it ran without problems.
    > Now, the errors have disappeared, so I guess everything is fine again.

    Please report it next time :)

    > BTW: I saw some warnings in the log file. I don't know if they're
    > interesting, but I thought I'd post them here:
    >
    > Schema (pid:16518):(m): Type net_nemein_tag_link
    > midgard-core (pid:16518):(m): Table and columns for
    > 'net_nemein_tag_link' OK
    > midgard-core (pid:16518):(WARNING): query failed: BLOB/TEXT column
    > 'fromClass' used in key specification without a key length

    It's harmless AFAIK. Core's table creation is not smart enough to handle
    already user's created/updated columns if they do not match core's way
    to do it.

    Piotras
    _______________________________________________
    user mailing list
    user@lists.midgard-project.org
    http://lists.midgard-project.org/mailman/listinfo/user
    •  Reply
    • stock-icons/16x16/stock_help-agent.png Report abuse
  4. Andreas Flack

    Re: [midgard-user] DB errors on executing purge_deleted.php

    Thu March 13 2008 20:10:11 UTC
    Piotr Pokora schrieb:
    > Andreas Flack writes:
    >> Hi!
    >
    > Hi!
    >
    >> The database in question was just updated from 2.6 running on a
    >> different server, where none of the components in question where
    >> installed (so the tables are all empty and so far unused). I ran
    >> datagard update multiple times and have TableCreate and TableUpdate set
    >> to true in the config file, but this doesn't fix those problems.
    >
    > TableCreate and TableUpdate are midgard-schema related.
    > So set them to true and run `midgard-schema configname` instead of datagard.
    >
    > Please, update to 1.8.7 before doing this as table create/update is
    > highly improved there.

    I already upgraded to 1.8.7 before upgrading. But apparently, it didn't
    help :-)

    >
    > Also you can set LogLevel to 'message' before running midgard-schema.
    > It will produce nice messages about what table is created/already
    > exists, and what column is created/already exist.

    I had tried that before, but all I got was a memory access error. The
    funny thing is that I tried it again now, and it ran without problems.
    Now, the errors have disappeared, so I guess everything is fine again.


    BTW: I saw some warnings in the log file. I don't know if they're
    interesting, but I thought I'd post them here:

    Schema (pid:16518):(m): Type net_nemein_tag_link
    midgard-core (pid:16518):(m): Table and columns for
    'net_nemein_tag_link' OK
    midgard-core (pid:16518):(WARNING): query failed: BLOB/TEXT column
    'fromClass' used in key specification without a key length


    Schema (pid:16518):(m): Type midcom_core_group_virtual_db
    midgard-core (pid:16518):(m): Table and columns for
    'midcom_core_group_virtual_db' OK
    midgard-core (pid:16518):(WARNING): query failed: BLOB/TEXT column
    'component' used in key specification without a key length


    Schema (pid:16518):(m): Type midcom_core_privilege_db
    midgard-core (pid:16518):(m): Table and columns for
    'midcom_core_privilege_db' OK
    midgard-core (pid:16518):(WARNING): query failed: BLOB/TEXT column
    'name' used in key specification without a key length


    Schema (pid:16518):(m): Type midcom_core_login_session_db
    midgard-core (pid:16518):(m): Table and columns for
    'midcom_core_login_session_db' OK
    midgard-core (pid:16518):(WARNING): query failed: BLOB/TEXT column
    'userid' used in key specification without a key length


    Schema (pid:16518):(m): Type org_openpsa_notifications_notification
    midgard-core (pid:16518):(m): Table and columns for
    'org_openpsa_notifications_notification' OK
    midgard-core (pid:16518):(WARNING): query failed: BLOB/TEXT column
    'action' used in key specification without a key length


    Schema (pid:16518):(m): Type org_openpsa_relatedto
    midgard-core (pid:16518):(m): Table and columns for
    'org_openpsa_relatedto' OK
    midgard-core (pid:16518):(WARNING): query failed: BLOB/TEXT column
    'toClass' used in key specification without a key length


    Schema (pid:16518):(m): Type org_openpsa_person
    midgard-core (pid:16518):(m): Table and columns for 'org_openpsa_person' OK
    midgard-core (pid:16518):(WARNING): query failed: Specified key was too
    long; max key length is 1000 bytes


    Schema (pid:16518):(m): Type org_openpsa_calendar_resource
    midgard-core (pid:16518):(m): Table and columns for
    'org_openpsa_calendar_resource' OK
    midgard-core (pid:16518):(WARNING): query failed: BLOB/TEXT column
    'location' used in key specification without a key length



    Bye, and thanks again!

    Andreas

    >
    > You can "redirect" all message from terminal to LogFile which is also
    > configurable.
    >
    > Piotras
    > _______________________________________________
    > user mailing list
    > user@lists.midgard-project.org
    > http://lists.midgard-project.org/mailman/listinfo/user

    _______________________________________________
    user mailing list
    user@lists.midgard-project.org
    http://lists.midgard-project.org/mailman/listinfo/user
    •  Reply
    • stock-icons/16x16/stock_help-agent.png Report abuse

Discussion

Copyright © 1999-2008 The Midgard Project. Open Content
Designed by Nemein, hosted by Anykey