Hey all,
I am seeing transactions wrapping my views without using the
'django.middleware.transaction.TransactionMiddleware'. I don't have
any @transaction decorators around my view. I also tried setting
DISABLE_TRANSACTION_MANAGEMENT to True as per:
http://docs.djangoproject.com/en/1.1/topics/db/transactions/ and that
didn't change anything. Where are these mysterious transactions being
set up from? The seem to be happening before the session is being
pulled for the view's request. I'm using Django 1.1 and PostgresSQL.
Thanks!
LOG: statement: SET DATESTYLE TO 'ISO'
LOG: statement: SHOW
client_encoding
LOG: statement: SHOW default_transaction_isolation
LOG: statement: BEGIN; SET TRANSACTION ISOLATION LEVEL READ
COMMITTED
LOG: statement: SET TIME ZONE E'America/Los_Angeles'
LOG: statement: SELECT "django_session"."session_key",
"django_session"."session_data", "django_session"."expire_date" FROM
"django_session" WHERE ("django_sessio
LOG: statement: SELECT "auth_user"."id", "auth_user"."username",
"auth_user"."first_name", "auth_user"."last_name",
"auth_user"."email", "auth_user"."password", "
LOG: statement: SELECT "trip_trip"."id", "trip_trip"."created_at",
"trip_trip"."updated_at", "trip_trip"."name",
"trip_trip"."description", "trip_trip"."announced
LOG: statement: SELECT "auth_user"."id", "auth_user"."username",
"auth_user"."first_name", "auth_user"."last_name",
"auth_user"."email", "auth_user"."password", "
LOG: statement: SELECT "auth_message"."id", "auth_message"."user_id",
"auth_message"."message" FROM "auth_message" WHERE
"auth_message"."user_id" = 1
LOG: statement: SELECT "locations_location"."id",
"locations_location"."created_at", "locations_location"."updated_at",
"locations_location"."type", "locations_lo
LOG: statement: SELECT "locations_location"."id",
"locations_location"."created_at", "locations_location"."updated_at",
"locations_location"."type", "locations_lo
LOG: statement: SELECT "locations_location"."id",
"locations_location"."created_at", "locations_location"."updated_at",
"locations_location"."type", "locations_lo
LOG: statement: SELECT "locations_location"."id",
"locations_location"."created_at", "locations_location"."updated_at",
"locations_location"."type", "locations_lo
LOG: statement: INSERT INTO "destinations_destination" ("created_at",
"updated_at", "status", "creator_id", "description", "location_id",
"trip_id", "enclosing_de
ERROR: duplicate key value violates unique constraint
"destinations_destination_trip_id_key"
STATEMENT: INSERT INTO "destinations_destination" ("created_at",
"updated_at", "status", "creator_id", "description", "location_id",
"trip_id", "enclosing_destina
LOG: statement: SELECT "destinations_destination"."id",
"destinations_destination"."created_at",
"destinations_destination"."updated_at", "destinations_destinatio
ERROR: current transaction is aborted, commands ignored until end of
transaction block
STATEMENT: SELECT "destinations_destination"."id",
"destinations_destination"."created_at",
"destinations_destination"."updated_at", "destinations_destination"."s
LOG: statement: ROLLBACK
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
