I confirm this, too (and mentioned it in another post a couple weeks back). I know I'll be digging into it soon as we prepare the admin for delivery to our client. We aren't going to chance them getting confused by six decimal places. Maybe we just need the truncate_decimal filter there?
Bb On Thu, Feb 19, 2009 at 9:20 PM, Evanlec <evan...@gmail.com> wrote: > > I can confirm this appears to happen as well to me. > Using PostgreSQL DB backend. > In the admin site both the prices and the number of items in stock > display with 6 decimal places. > Don't know if it's related to PgSQL or not.... > > On Feb 18, 4:13 pm, Trent <tjurew...@gmail.com> wrote: > > I am having an issue only in my PRODUCTION environment running a > > PostgreSQL DB. When I create a new product, the pricing defaults to 6 > > decimal places. For example, I create a product and set the price to > > 99.99, the upon saving the product, the price changes to 99.990000. > > This gets corrected on the display of the pricing in the store, but > > the order confirmation email displays a price with 6 decimal places. > > I've seen a few other threads about decimal places on PostgreSQL, but > > nothing recent and no instructions to fix the problem. Can anybody > > confirm this behavior and perhaps offer a remedy? > > > > Thanks! > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to satchmo-users@googlegroups.com To unsubscribe from this group, send email to satchmo-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
