Small update: Wrapping the view function with *@transaction.atomic* fixes
the issue -- the queries execute in a transaction as expected.
So I guess my immediate problem is resolved.
If anyone has an idea, I'd still love to know why the view is ignoring the
top-level TRANSACTION_ATOMIC setting.
Hi All,
I have ATOMIC_REQUESTS set to True in my database configuration:
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.postgresql_psycopg2',
'NAME': 'abcd',
'USER': 'user',
'PASSWORD': '',
'HOST': '',
'PORT': '',
'ATOMIC_REQUESTS': True,
}
}
But I started getting the following error
on every page view? Are there any other downsides to this
kind of setup? Or alternative ways of 'versioning' groups of keys?
Thanks in advance.
- EJ
CACHES = {
'default': {
"VERSION": 1,
"BACKEND": "django_redis.cache.RedisCache&quo
Hi Tim,
Good idea, but that won't work unfortunately as we use the 'Site'
functionality between the 40-odd sites.
Thanks though!
Ethan
On Sep 28, 7:50 pm, "Tim Sawyer" wrote:
> > Hi all,
>
> > I'm trying to have comments on my sites shown on all other sites, as I
> > have a 'mobile' skin for m
Hi all,
I'm trying to have comments on my sites shown on all other sites, as I
have a 'mobile' skin for my site on a separate domain and site_id.
So for example:
Joe posts a comment on http://www.site1.mydomain.com
Mary goes to http://www.mobilesite.mydomain.com and can see and
respond to Joe's
Hi guys, thanks a lot for your help!
Dmitry Dulepov wrote:
> > a) It's not the standard. I've looked around at subversion repository
> > tutorials but can't seem to wrap my head around applying that to our
> > software.
>
> Why not the standard? Many large companies do it the same way as you do.
Hi guys, first of all: Thanks! Django-users has been a great resource
for me so far; I've come across many solutions for my own problems
here.
I'm not even really sure if this question is totally appropriate for
this page, but here goes:
I'm a new developer working on a small social networking we
7 matches
Mail list logo
