Thanks :) Looks like this is the solution to our problem. We haven't tested it yet but will try soon.
Thanks again On 9/20/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > > On 9/19/07, Landlord Bulfleet <[EMAIL PROTECTED]> wrote: > ... > > > > sum is property of a model object in our database > > (models.DecimalField(max_digits=7, decimal_places=2)) & f_c.rate is a > > Decimal constructed using Decimal(string) construction (Decimal is > imported > > with "from decimal import Decimal") > > > > We have some doubts that this may be a result of the django's python 2.3 > > _decimal compatibility. > > You're using PsycoPG with multiple interpreters. :) > > http://www.initd.org/tracker/psycopg/ticket/192 > > http://groups.google.com/group/django-developers/browse_thread/thread/63046b2fca27673c/898dbf8da327ce71 > > Anyway, I did run into this using psycopg1, but switched to psycopg2 > and patched it since 1) it's being maintained and 2) it was easier to > fix that way. > > I emailed the psycopg list a couple weeks ago with a patch but never > heard back from them. I don't have rights to add the patch to their > ticket tracker, or I'd do that, too. > > I'm attaching a patch against psycopg2's source code here. This is > for r896 on the 2.0.x branch. > > Alternatively, you could run separate apache processes for each needed > interpreter or switch to mod_wsgi. > > I wasn't prepared to swtich to mod_wsgi in a hurry, so patched > psycopg2 instead. > > Apparently not that many people are using multiple interpreters and > decimal fields with psycopg... > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
