MMBase

It is impossible to delete builders

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.7.2
  • Fix Version/s: 1.7.3
  • Component/s: Builders
  • Description:
    Hide
    original bugid: #6641
    A normal procedure for deleting builders cq. nodetypes you no longer need would (could?) be as follows:
    1. Delete all nodes of the nodetype you wish to remove
    2. Remove all relation types (reltype) that use that nodetype
    3. Delete the nodetype from objecttype (typedef)
    4. Remove the builder definition from your configuration

    At step 3 you will get the following errors: 'org.apache.jasper.JasperException: Could not delete builder config' or 'org.apache.jasper.JasperException: I can only delete active builders(otherwise we table's could stay in database..)'. The first one is on an active builder, the next one on a builder already removed from your configuration or set 'inactive'.

    See also bug #5830
    Copied some code that was already in 1.8. Now checks whether the to-be-deleted builder still contains nodes or has references in either typerel or typedef. Deleting should still fail when the configuration file can not be removed (normally this is because of file permissions, but that can not be considered a MMBase bug imho).

    The builders table still remains in the database. Is that a bug?
    Show
    original bugid: #6641 A normal procedure for deleting builders cq. nodetypes you no longer need would (could?) be as follows: 1. Delete all nodes of the nodetype you wish to remove 2. Remove all relation types (reltype) that use that nodetype 3. Delete the nodetype from objecttype (typedef) 4. Remove the builder definition from your configuration At step 3 you will get the following errors: 'org.apache.jasper.JasperException: Could not delete builder config' or 'org.apache.jasper.JasperException: I can only delete active builders(otherwise we table's could stay in database..)'. The first one is on an active builder, the next one on a builder already removed from your configuration or set 'inactive'. See also bug #5830 Copied some code that was already in 1.8. Now checks whether the to-be-deleted builder still contains nodes or has references in either typerel or typedef. Deleting should still fail when the configuration file can not be removed (normally this is because of file permissions, but that can not be considered a MMBase bug imho). The builders table still remains in the database. Is that a bug?

Activity

Hide
André van Toly added a comment - 2005-01-04 11:21
It is impossible to delete builders
A normal procedure for deleting builders cq. nodetypes you no longer need would (could?) be as follows:
1. Delete all nodes of the nodetype you wish to remove
2. Remove all relation types (reltype) that use that nodetype
3. Delete the nodetype from objecttype (typedef)
4. Remove the builder definition from your configuration

At step 3 you will get the following errors: 'org.apache.jasper.JasperException: Could not delete builder config' or 'org.apache.jasper.JasperException: I can only delete active builders(otherwise we table's could stay in database..)'. The first one is on an active builder, the next one on a builder already removed from your configuration or set 'inactive'.

See allso bug #5830
Show
André van Toly added a comment - 2005-01-04 11:21 It is impossible to delete builders A normal procedure for deleting builders cq. nodetypes you no longer need would (could?) be as follows: 1. Delete all nodes of the nodetype you wish to remove 2. Remove all relation types (reltype) that use that nodetype 3. Delete the nodetype from objecttype (typedef) 4. Remove the builder definition from your configuration At step 3 you will get the following errors: 'org.apache.jasper.JasperException: Could not delete builder config' or 'org.apache.jasper.JasperException: I can only delete active builders(otherwise we table's could stay in database..)'. The first one is on an active builder, the next one on a builder already removed from your configuration or set 'inactive'. See allso bug #5830
Hide
André van Toly added a comment - 2005-01-05 10:17
It is impossible to delete builders
A normal procedure for deleting builders cq. nodetypes you no longer need would (could?) be as follows:
1. Delete all nodes of the nodetype you wish to remove
2. Remove all relation types (reltype) that use that nodetype
3. Delete the nodetype from objecttype (typedef)
4. Remove the builder definition from your configuration

At step 3 you will get the following errors: 'org.apache.jasper.JasperException: Could not delete builder config' or 'org.apache.jasper.JasperException: I can only delete active builders(otherwise we table's could stay in database..)'. The first one is on an active builder, the next one on a builder already removed from your configuration or set 'inactive'.

See also bug #5830
Copied some code that was already in 1.8. Now checks whether the to-be-deleted builder still contains nodes or has references in either typerel or typedef. Deleting should still fail when the configuration file can not be removed (normally this is because of file permissions, but that can not be considered a MMBase bug imho).

The builders table still remains in the database. Is that a bug?
Show
André van Toly added a comment - 2005-01-05 10:17 It is impossible to delete builders A normal procedure for deleting builders cq. nodetypes you no longer need would (could?) be as follows: 1. Delete all nodes of the nodetype you wish to remove 2. Remove all relation types (reltype) that use that nodetype 3. Delete the nodetype from objecttype (typedef) 4. Remove the builder definition from your configuration At step 3 you will get the following errors: 'org.apache.jasper.JasperException: Could not delete builder config' or 'org.apache.jasper.JasperException: I can only delete active builders(otherwise we table's could stay in database..)'. The first one is on an active builder, the next one on a builder already removed from your configuration or set 'inactive'. See also bug #5830 Copied some code that was already in 1.8. Now checks whether the to-be-deleted builder still contains nodes or has references in either typerel or typedef. Deleting should still fail when the configuration file can not be removed (normally this is because of file permissions, but that can not be considered a MMBase bug imho). The builders table still remains in the database. Is that a bug?

People

Dates

  • Created:
    2005-01-05 10:17
    Updated:
    2006-11-24 13:47
    Resolved:
    2006-11-24 13:47