I'm biased, of course, but I'd recommend using my extension, Semantic Internal Objects:


I think it's a better solution for compound data than multi-valued properties, for several reasons, among them the difficulty of parsing out data that's stored with multi-valued properties.


On Sun, Oct 18, 2009 at 1:02 PM, Phlox <makthorpe@gmail.com> wrote:
I have the feeling I am overlooking something terribly obvious and perhaps someone can point out what obvious place I have left my glasses.

I have a number in an N-ary property with a number.  Plain output (?<property># -) does not give me numbers without commas.  If I feed the number into an expr: with a comma, then it complains about it.  I can strip the comma with a #replace, or I can produce comma less numbers by bogusly declaring the number as a Date.

Help:custom units describes creating custom datatypes, but it's not clear to me from the docs I can use this to remove the commas.

Does anyone have a tidier solution to the goal of getting a value that can be numerically range searched but does not format it in a way that makes #expr complain?


Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
Semediawiki-user mailing list