Bug 689 – HopObject.list() different behaviour for transient vs persisted object

Bug 689 - HopObject.list() different behaviour for transient vs persisted object

Summary:

HopObject.list() different behaviour for transient vs persisted object

Status:	RESOLVED FIXED

Product:	Helma
Component:	Database Layer
Version:	CVS trunk
Platform:	Other Linux

Importance:	P5 normal
Target Milestone:	1.7.0
Assigned To:	Helma Developer Mailing List

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-11-03 10:48 by s o
Modified:	2009-11-05 09:12 (History)

Attachments
stack trace NPE list(x,y) (1.59 KB, text/plain) 2009-11-03 10:49, s o	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From s o 2009-11-03 10:48:16

if the object is transient a call to list() with the min and/or max argument
will result in NPE. this works for persisted objects.

{{{
var foo = new FooProto();
foo.list(); // works
foo.list(0,10); // NPE fail
}}}

if persisted all is good:

{{{
var foo = FooProto.get(0);
foo.list();
foo.list(0, 10);
}}}

------- Comment #1 From s o 2009-11-03 10:49:04 -------

Created an attachment (id=125) [details]
stack trace NPE list(x,y)

------- Comment #2 From Hannes Wallnoefer 2009-11-04 12:02:16 -------

Fixed in svn.

------- Comment #3 From s o 2009-11-04 17:27:09 -------

still broken with current svn head, easy to reproduce:

{{{

Root.prototype.testlist_action = function() 
   var hopObj = new HopObject();
   hopObj.list(); // works
   hopObj.list(0,10); // NPE
}

}}}

------- Comment #4 From Hannes Wallnoefer 2009-11-05 09:12:09 -------

Fixed that one too.