Thanks for your response, i should have searched the previous discussions on this subject my appologies. it seemed indeed that a previous db call issued the problem.
thanks again, richard On Sep 10, 12:22 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > On 9/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > the problem that occured while putting the same code on the server is > > a Time Zone Error. > > No, it is not. Read the error message carefully: PostgreSQL is not > saying the SET TIME ZONE was problematic, it is saying "an error > occurred in one of your earlier queries and I am refusing to process > anything else until you roll back your transaction". > > Searching the archives of this list, or the Django ticket tracker, > would have turned up several discussions of this. > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
