I would have to agree, BigDecimal would be nice in the app engine. Storing as a String presents the sorting challenge.
Double, Float, Long just won't work for money and latitude and longitude. And money has to do with everything. App Engine is storing phone numbers, ratings, and other objects, why not BigDecimal? Even the geo points need more precision. Geocoding spits out a double, and App Engine wants a float, that won't work either. BigDecimal is what geocoded coordinates should go into. Basically a String, with numeric sorting I think? Just a thought, Brandon Donnelson http://gwt-examples.googlecode.com -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
