I\'m still having big problems with BigDecimal (the trail of tears started here, and continued to here so far.
Now I\'ve got the opposite problem - going from BigDec
So how can I manipulate the BigDecimal value in the so that it will be accepted by the ContentValues instance?
Well, you can call doubleValue() on the BigDecimal to downgrade it to a double, which can go in the ContentValues (after autoboxing it to a Double). Or, you can store its string representation in a TEXT column. Or, you can store the unscaledValue() and scale() in two INTEGER columns.
But SQLite's closest match is REAL
No, it is not.
You seem to be interested in storing pricing data in SQLite. A search for storing prices in sqlite on a major search engine turns up:
The consensus is to store the value as an INTEGER column, priced in the smallest individual currency unit (e.g., cents for currency values in US dollars), or something else as appropriate (e.g., tenths of a cent if that's the finest granularity of the prices).
Your POJO would then hold int values to match.