MMBase

Null in integer fields, leads to nullpointer exceptions

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.6.1
  • Fix Version/s: 1.6.4
  • Component/s: Core
  • Description:
    Hide
    original bugid: #6034
    Stacktrace:

      java.lang.NullPointerException
    at java.util.Hashtable.put(Hashtable.java:375)
    at org.mmbase.module.core.MMObjectNode.storeValue(Unknown Source)
    at org.mmbase.module.core.MMObjectNode.setValue(Unknown Source)
    at org.mmbase.storage.database.SQL92DatabaseStorage.loadFieldFromTable(Unknown Source)
    at org.mmbase.storage.database.Support2Storage.decodeDBnodeField(Unknown Source)
    at org.mmbase.module.core.MMObjectBuilder.readSearchResults(Unknown Source)
    at org.mmbase.module.core.MMObjectBuilder.getList(Unknown Source)
    at org.mmbase.module.core.MMObjectBuilder.searchList(Unknown Source)
    at org.mmbase.bridge.implementation.BasicNodeManager.getList(Unknown Source)
    at org.mmbase.bridge.jsp.taglib.ListNodesTag.doStartTag(Unknown Source)



    This happens after doing a manual alter table, which was not smart enough evidently. But why throwing a nullpointer then.
    When 'storing' null values in a node, the field is now removed from the values list.
    This may be a step towards a databaselayer where we can actually store null values in a table (rather than storing empty strings or the numeric -1).
    Show
    original bugid: #6034 Stacktrace:   java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:375) at org.mmbase.module.core.MMObjectNode.storeValue(Unknown Source) at org.mmbase.module.core.MMObjectNode.setValue(Unknown Source) at org.mmbase.storage.database.SQL92DatabaseStorage.loadFieldFromTable(Unknown Source) at org.mmbase.storage.database.Support2Storage.decodeDBnodeField(Unknown Source) at org.mmbase.module.core.MMObjectBuilder.readSearchResults(Unknown Source) at org.mmbase.module.core.MMObjectBuilder.getList(Unknown Source) at org.mmbase.module.core.MMObjectBuilder.searchList(Unknown Source) at org.mmbase.bridge.implementation.BasicNodeManager.getList(Unknown Source) at org.mmbase.bridge.jsp.taglib.ListNodesTag.doStartTag(Unknown Source) This happens after doing a manual alter table, which was not smart enough evidently. But why throwing a nullpointer then. When 'storing' null values in a node, the field is now removed from the values list. This may be a step towards a databaselayer where we can actually store null values in a table (rather than storing empty strings or the numeric -1).

Activity

Hide
Michiel Meeuwissen added a comment - 2003-04-28 11:18
Null in integer fields, leads to nullpointer exceptions
Stacktrace:

  java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:375)
at org.mmbase.module.core.MMObjectNode.storeValue(Unknown Source)
at org.mmbase.module.core.MMObjectNode.setValue(Unknown Source)
at org.mmbase.storage.database.SQL92DatabaseStorage.loadFieldFromTable(Unknown Source)
at org.mmbase.storage.database.Support2Storage.decodeDBnodeField(Unknown Source)
at org.mmbase.module.core.MMObjectBuilder.readSearchResults(Unknown Source)
at org.mmbase.module.core.MMObjectBuilder.getList(Unknown Source)
at org.mmbase.module.core.MMObjectBuilder.searchList(Unknown Source)
at org.mmbase.bridge.implementation.BasicNodeManager.getList(Unknown Source)
at org.mmbase.bridge.jsp.taglib.ListNodesTag.doStartTag(Unknown Source)



This happens after doing a manual alter table, which was not smart enough evidently. But why throwing a nullpointer then.
Show
Michiel Meeuwissen added a comment - 2003-04-28 11:18 Null in integer fields, leads to nullpointer exceptions Stacktrace:   java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:375) at org.mmbase.module.core.MMObjectNode.storeValue(Unknown Source) at org.mmbase.module.core.MMObjectNode.setValue(Unknown Source) at org.mmbase.storage.database.SQL92DatabaseStorage.loadFieldFromTable(Unknown Source) at org.mmbase.storage.database.Support2Storage.decodeDBnodeField(Unknown Source) at org.mmbase.module.core.MMObjectBuilder.readSearchResults(Unknown Source) at org.mmbase.module.core.MMObjectBuilder.getList(Unknown Source) at org.mmbase.module.core.MMObjectBuilder.searchList(Unknown Source) at org.mmbase.bridge.implementation.BasicNodeManager.getList(Unknown Source) at org.mmbase.bridge.jsp.taglib.ListNodesTag.doStartTag(Unknown Source) This happens after doing a manual alter table, which was not smart enough evidently. But why throwing a nullpointer then.
Hide
Pierre van Rooden added a comment - 2003-05-01 09:25
Null in integer fields, leads to nullpointer exceptions
Stacktrace:

  java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:375)
at org.mmbase.module.core.MMObjectNode.storeValue(Unknown Source)
at org.mmbase.module.core.MMObjectNode.setValue(Unknown Source)
at org.mmbase.storage.database.SQL92DatabaseStorage.loadFieldFromTable(Unknown Source)
at org.mmbase.storage.database.Support2Storage.decodeDBnodeField(Unknown Source)
at org.mmbase.module.core.MMObjectBuilder.readSearchResults(Unknown Source)
at org.mmbase.module.core.MMObjectBuilder.getList(Unknown Source)
at org.mmbase.module.core.MMObjectBuilder.searchList(Unknown Source)
at org.mmbase.bridge.implementation.BasicNodeManager.getList(Unknown Source)
at org.mmbase.bridge.jsp.taglib.ListNodesTag.doStartTag(Unknown Source)



This happens after doing a manual alter table, which was not smart enough evidently. But why throwing a nullpointer then.
When 'storing' null values in a node, the field is now removed from the values list.
This may be a step towards a databaselayer where we can actually store null values in a table (rather than storing empty strings or the numeric -1).
Show
Pierre van Rooden added a comment - 2003-05-01 09:25 Null in integer fields, leads to nullpointer exceptions Stacktrace:   java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:375) at org.mmbase.module.core.MMObjectNode.storeValue(Unknown Source) at org.mmbase.module.core.MMObjectNode.setValue(Unknown Source) at org.mmbase.storage.database.SQL92DatabaseStorage.loadFieldFromTable(Unknown Source) at org.mmbase.storage.database.Support2Storage.decodeDBnodeField(Unknown Source) at org.mmbase.module.core.MMObjectBuilder.readSearchResults(Unknown Source) at org.mmbase.module.core.MMObjectBuilder.getList(Unknown Source) at org.mmbase.module.core.MMObjectBuilder.searchList(Unknown Source) at org.mmbase.bridge.implementation.BasicNodeManager.getList(Unknown Source) at org.mmbase.bridge.jsp.taglib.ListNodesTag.doStartTag(Unknown Source) This happens after doing a manual alter table, which was not smart enough evidently. But why throwing a nullpointer then. When 'storing' null values in a node, the field is now removed from the values list. This may be a step towards a databaselayer where we can actually store null values in a table (rather than storing empty strings or the numeric -1).
Hide
Pierre van Rooden added a comment - 2003-05-01 09:26
Null in integer fields, leads to nullpointer exceptions
Stacktrace:

  java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:375)
at org.mmbase.module.core.MMObjectNode.storeValue(Unknown Source)
at org.mmbase.module.core.MMObjectNode.setValue(Unknown Source)
at org.mmbase.storage.database.SQL92DatabaseStorage.loadFieldFromTable(Unknown Source)
at org.mmbase.storage.database.Support2Storage.decodeDBnodeField(Unknown Source)
at org.mmbase.module.core.MMObjectBuilder.readSearchResults(Unknown Source)
at org.mmbase.module.core.MMObjectBuilder.getList(Unknown Source)
at org.mmbase.module.core.MMObjectBuilder.searchList(Unknown Source)
at org.mmbase.bridge.implementation.BasicNodeManager.getList(Unknown Source)
at org.mmbase.bridge.jsp.taglib.ListNodesTag.doStartTag(Unknown Source)



This happens after doing a manual alter table, which was not smart enough evidently. But why throwing a nullpointer then.
When 'storing' null values in a node, the field is now removed from the values list.
This may be a step towards a databaselayer where we can actually store null values in a table (rather than storing empty strings or the numeric -1).
Show
Pierre van Rooden added a comment - 2003-05-01 09:26 Null in integer fields, leads to nullpointer exceptions Stacktrace:   java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:375) at org.mmbase.module.core.MMObjectNode.storeValue(Unknown Source) at org.mmbase.module.core.MMObjectNode.setValue(Unknown Source) at org.mmbase.storage.database.SQL92DatabaseStorage.loadFieldFromTable(Unknown Source) at org.mmbase.storage.database.Support2Storage.decodeDBnodeField(Unknown Source) at org.mmbase.module.core.MMObjectBuilder.readSearchResults(Unknown Source) at org.mmbase.module.core.MMObjectBuilder.getList(Unknown Source) at org.mmbase.module.core.MMObjectBuilder.searchList(Unknown Source) at org.mmbase.bridge.implementation.BasicNodeManager.getList(Unknown Source) at org.mmbase.bridge.jsp.taglib.ListNodesTag.doStartTag(Unknown Source) This happens after doing a manual alter table, which was not smart enough evidently. But why throwing a nullpointer then. When 'storing' null values in a node, the field is now removed from the values list. This may be a step towards a databaselayer where we can actually store null values in a table (rather than storing empty strings or the numeric -1).
Hide
Pierre van Rooden added a comment - 2003-05-01 09:26
Null in integer fields, leads to nullpointer exceptions
Stacktrace:

  java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:375)
at org.mmbase.module.core.MMObjectNode.storeValue(Unknown Source)
at org.mmbase.module.core.MMObjectNode.setValue(Unknown Source)
at org.mmbase.storage.database.SQL92DatabaseStorage.loadFieldFromTable(Unknown Source)
at org.mmbase.storage.database.Support2Storage.decodeDBnodeField(Unknown Source)
at org.mmbase.module.core.MMObjectBuilder.readSearchResults(Unknown Source)
at org.mmbase.module.core.MMObjectBuilder.getList(Unknown Source)
at org.mmbase.module.core.MMObjectBuilder.searchList(Unknown Source)
at org.mmbase.bridge.implementation.BasicNodeManager.getList(Unknown Source)
at org.mmbase.bridge.jsp.taglib.ListNodesTag.doStartTag(Unknown Source)



This happens after doing a manual alter table, which was not smart enough evidently. But why throwing a nullpointer then.
When 'storing' null values in a node, the field is now removed from the values list.
This may be a step towards a databaselayer where we can actually store null values in a table (rather than storing empty strings or the numeric -1).
Show
Pierre van Rooden added a comment - 2003-05-01 09:26 Null in integer fields, leads to nullpointer exceptions Stacktrace:   java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:375) at org.mmbase.module.core.MMObjectNode.storeValue(Unknown Source) at org.mmbase.module.core.MMObjectNode.setValue(Unknown Source) at org.mmbase.storage.database.SQL92DatabaseStorage.loadFieldFromTable(Unknown Source) at org.mmbase.storage.database.Support2Storage.decodeDBnodeField(Unknown Source) at org.mmbase.module.core.MMObjectBuilder.readSearchResults(Unknown Source) at org.mmbase.module.core.MMObjectBuilder.getList(Unknown Source) at org.mmbase.module.core.MMObjectBuilder.searchList(Unknown Source) at org.mmbase.bridge.implementation.BasicNodeManager.getList(Unknown Source) at org.mmbase.bridge.jsp.taglib.ListNodesTag.doStartTag(Unknown Source) This happens after doing a manual alter table, which was not smart enough evidently. But why throwing a nullpointer then. When 'storing' null values in a node, the field is now removed from the values list. This may be a step towards a databaselayer where we can actually store null values in a table (rather than storing empty strings or the numeric -1).

People

Dates

  • Created:
    2003-05-01 09:26
    Updated:
    2006-11-24 12:39
    Resolved:
    2006-11-24 12:39