Reported by Andrea Gronchi, Dec 14, 2009
Hello. In case of setlocale(), Pluf's default float-2-db policy formats a string using the locale-aware decimal point. As a result, the DB will probably fail parsing it. (Or at least, in my case PostgreSQL 8.4 did). I don't know if Pluf is supposed to work or not in conjunction with setlocale(), however I implemented Pluf_DB_FloatFromDb() and Pluf_DB_FloatToDb() to be non location-aware as a workaround. Please find the attached patch in case it helps. Thanks, Andrea.
Comment 1 by Loïc d'Anterroches, Jan 20, 2010
I have been pondering this issue a lot. I still don't know if using setlocale is good or not. For your patch, it looks like it breaks nothing when not using setlocale, so I am going to apply it (but not now because I am falling asleep).
Sign in to reply to this comment.