Hmm. Alright.. lol. I'm not sure how I"ll be able to solve this problem, but thanks! I'll definitely try examining the issue thoroughly!
On Apr 28, 9:56 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > On 4/28/07, Roboto <[EMAIL PROTECTED]> wrote: > > > I'm using Piotr Diamanda MyghtyBoard and I keep running into this > > error when I try this 1 particular view... I've asked Piotr directly > > and he indicated it could be a django/server issue. Any thoughts? > > If you search on the Django ticket tracker you'll find several > references to this; the time zone has *nothing* to do with it. > Postgres operates differently from other databases in that it is > fairly strict about errors, and by default everything you do in > Postgres with Django is inside a transaction. > > What's happened is that some bad SQL has been sent at some previous > point, and so the ongoing transaction in Postgres will refuse to > accept any more SQL until a ROLLBACK command is issued within the > transaction (you can do this manually in Django if need be). Django > sends the SET TIME ZONE query fairly often, in order to tell the DB > what format to return date and time fields in, and it just so happens > that fairly often that's the first query sent *after* the one which > caused the error, and so is the first one which returns the > "transaction aborted" message. > > -- > "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 -~----------~----~----~----~------~----~------~--~---
