> When line 7 is uncommented, transaction management is
> enabled, and the view works as I would expect.
So it is, my bad, thank you againg.
You see, it seemed a little weird, that first (with the decorator) we
force transaction to commit manually to use 'test' for all that would
happen in our vi
> When line 7 is uncommented, transaction management is
> enabled, and the view works as I would expect.
So it is, my bad, thank you againg.
You see, it seemed a little weird, that first (with the decorator) we
force transaction to commit manually to 'test' all that would happen
in our view (supp
> When line 7 is uncommented, transaction management is
> enabled, and the view works as I would expect.
So it is, my bad, Russ, thank you againg.
You see, it seemed a little weird, that first (with the decorator) we
force transaction to commit manually to 'test' all that would happen
in our view
On Thu, Apr 29, 2010 at 12:20 PM, idle sign wrote:
> I'm using the latest trunk from http://github.com/django/django.
> A complete test project you can grab at
> http://idlesign.narod.ru/django/django-tests.tar.gz
> There is a little bootstrap.sh to run to create DBs.
>
> Thank you, Russ.
Ok - u
I'm using the latest trunk from http://github.com/django/django.
A complete test project you can grab at
http://idlesign.narod.ru/django/django-tests.tar.gz
There is a little bootstrap.sh to run to create DBs.
Thank you, Russ.
On 29 апр, 10:16, Russell Keith-Magee wrote:
> On Thu, Apr 29, 2010
On Thu, Apr 29, 2010 at 11:04 AM, idle sign wrote:
> I thought so, have tried so, but got "This code isn't under
> transaction management", and opened this thread :)
I get that error if I *omit* the using= argument to commit (which is
what I'd expect to see).
What version of trunk are you using?
I thought so, have tried so, but got "This code isn't under
transaction management", and opened this thread :)
Environment:
Request Method: GET
Request URL: http://localhost:8000/
Django Version: 1.2 beta 1
Python Version: 2.6.4
Installed Applications:
['testapp']
Installed Middleware:
('django.m
On Thu, Apr 29, 2010 at 12:59 AM, idle sign wrote:
> I think I spotted something weird. May be someone could explain that?
>
> 1. In Django 1.2 define two DBs (let it be sqlite), one of which name
> 'test'.
> 2. Define DB router for 'testapp' so that it always uses 'test' DB.
> 3. Use 'commit_manu
I think I spotted something weird. May be someone could explain that?
1. In Django 1.2 define two DBs (let it be sqlite), one of which name
'test'.
2. Define DB router for 'testapp' so that it always uses 'test' DB.
3. Use 'commit_manually' decorator for 'test' view.
4. In 'test' view define 'curs
On 7/25/07, Andrey Khavryuchenko <[EMAIL PROTECTED]> wrote:
>
> Nimrod,
>
> NAA> On 7/25/07, Andrey Khavryuchenko <[EMAIL PROTECTED]> wrote:
> >> >> Yes, I read carefuly your question and thought the answer was
> >> >> straighforward. I don't understand why you don't want decorators,
> but y
Nimrod,
NAA> On 7/25/07, Andrey Khavryuchenko <[EMAIL PROTECTED]> wrote:
>> >> Yes, I read carefuly your question and thought the answer was
>> >> straighforward. I don't understand why you don't want decorators, but
>> >> you
>> >> could just check the decorator definition to read what i
Hello Andrey,
> NAA> On 7/25/07, Andrey Khavryuchenko <[EMAIL PROTECTED]> wrote:
> >> Yes, I read carefuly your question and thought the answer was
> >> straighforward. I don't understand why you don't want decorators, but
> you
> >> could just check the decorator definition to read what i
NAA> On 7/25/07, Andrey Khavryuchenko <[EMAIL PROTECTED]> wrote:
>> Yes, I read carefuly your question and thought the answer was
>> straighforward. I don't understand why you don't want decorators, but you
>> could just check the decorator definition to read what it does and copy
>> it's
Hello everyone,
On 7/25/07, Andrey Khavryuchenko <[EMAIL PROTECTED]> wrote:
> Yes, I read carefuly your question and thought the answer was
> straighforward. I don't understand why you don't want decorators, but you
> could just check the decorator definition to read what it does and copy
> it'
On 7/25/07, Peter Melvyn <[EMAIL PROTECTED]> wrote:
>
> > Your example is correct, and you aren't violating any 'Django principles'.
>
> Really? Should not be there something like this?
Yes - this is a more complete example, and catching the rollback case
is a good idea. The point I was trying to
Michal,
MK> I suppose you read my question attentively and therefore you know that
MK> I searched the web (and django documentation of course including the
MK> transaction page). And I suppose you know that I was looking for
MK> example how to use transactions without decorators.
MK> The pr
> Your example is correct, and you aren't violating any 'Django principles'.
Really? Should not be there something like this?
enter_transaction_management()
try:
managed(True)
try:
...
except:
transaction.rollback()
raise ...
else:
tra
OK, I can try it but it will require a correction because I'm not a
native speaker.
Michal
On 24/07/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> On 7/24/07, Michal Konvalinka <[EMAIL PROTECTED]> wrote:
> >
> > The problem is that there's no example how to use transactions without
> > de
On 7/24/07, Michal Konvalinka <[EMAIL PROTECTED]> wrote:
>
> The problem is that there's no example how to use transactions without
> decorators in the documentation, there's no example here in this
> mailing list... I found the example in
> django.db.transaction.py
This is a problem that should
Hi Andrey,
I suppose you read my question attentively and therefore you know that
I searched the web (and django documentation of course including the
transaction page). And I suppose you know that I was looking for
example how to use transactions without decorators.
The problem is that there's n
MK> Hi,
MK> I would like to use transactions (in MySQL and InnoDB). I know there
MK> are decorators but I don't want to use them now. Is there any example
MK> how to use transactions without decorators? I couldn't find anything
MK> on django website, this user-group...
Quick google on "djan
On 7/24/07, Michal Konvalinka <[EMAIL PROTECTED]> wrote:
> It works but I would like to ask If I am violating some Django
> principles or not.
Your example is correct, and you aren't violating any 'Django principles'.
Django provides decorators because it can be convenient to wrap a
whole funct
Hi,
I would like to use transactions (in MySQL and InnoDB). I know there
are decorators but I don't want to use them now. Is there any example
how to use transactions without decorators? I couldn't find anything
on django website, this user-group...
Is this correct?
def update_something(self, pa
23 matches
Mail list logo
