Re: [Django] #27620: Add a TransactionMiddleware

[Django]

#27620: Add a TransactionMiddleware
--+
 Reporter:  Tim Graham|Owner:  (none)
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018e50592aec-24115d37-eef6-4918-8361-262616efc4c8-00%40eu-central-1.amazonses.com.

Re: [Django] #27620: Add a TransactionMiddleware

[Django]

#27620: Add a TransactionMiddleware
--+
 Reporter:  Tim Graham|Owner:  (none)
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Mariusz Felisiak):

 * owner:  luojiebin => (none)
 * status:  assigned => new


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070181ae5dc319-76ded3d6-6502-4b8a-a8d3-a044a5d8b590-00%40eu-central-1.amazonses.com.

Re: [Django] #27620: Add a TransactionMiddleware

[Django]

#27620: Add a TransactionMiddleware
--+-
 Reporter:  Tim Graham|Owner:  luojiebin
 Type:  New feature   |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by luojiebin):

 But why the previous TransactionMiddleware was deprecated? Only because
 ATOMIC_REQUESTS can do the same thing as it? But it can not noly apply to
 views, but also other middleware, which ATOMIC_REQUESTS can't do. So, does
 the previous TransactionMiddleware cause any problem so that we have to
 deprecate it? With the new-style middleware, we can handle the previous
 problem, or we can add new feature to TransactionMiddlware with it?

   to [comment:4 Florian Apolloner]:
 > @luojiebin That is to be decided, the main issue here - as you noted -
 is supporting
 
[https://docs.djangoproject.com/en/1.10/topics/db/transactions/#django.db.transaction.non_atomic_requests
 non_atomic_requests]. Any ideas welcome :D

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.eeb1accf51b31584827198a9803a6fbb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27620: Add a TransactionMiddleware

[Django]

#27620: Add a TransactionMiddleware
--+-
 Reporter:  Tim Graham|Owner:  luojiebin
 Type:  New feature   |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by Florian Apolloner):

 @luojiebin That is to be decided, the main issue here - as you noted - is
 supporting
 
[https://docs.djangoproject.com/en/1.10/topics/db/transactions/#django.db.transaction.non_atomic_requests
 non_atomic_requests]. Any ideas welcome :D

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.e7c77708ef15353047e61359a1f706db%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27620: Add a TransactionMiddleware

[Django]

#27620: Add a TransactionMiddleware
--+-
 Reporter:  Tim Graham|Owner:  luojiebin
 Type:  New feature   |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by Tim Graham):

 * cc: Florian Apolloner (added)


Comment:

 Florian (apollo13) mentioned this idea in #django-dev IRC but later
 indicated there may be some problems with it.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.4baa6a4442ec68f7662337f577b0df5d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27620: Add a TransactionMiddleware

[Django]

#27620: Add a TransactionMiddleware
--+-
 Reporter:  Tim Graham|Owner:  luojiebin
 Type:  New feature   |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by luojiebin):

 Do this middleware want to do the same thing as the one in Django 1.7
 except that it applies only to view functions, not including those
 middleware modules coming after it? Can you explain it in more detail?
 Thanks.
  to [ticket:27620 Tim Graham]:
 > With new-style middleware, it should be feasible to write a
 `TransactionMiddleware` that works properly (as opposed to the version in
 Django 1.7 and older).

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.ab0cc3a7bba803be3d7142f05d39002f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27620: Add a TransactionMiddleware

[Django]

#27620: Add a TransactionMiddleware
--+-
 Reporter:  Tim Graham|Owner:  luojiebin
 Type:  New feature   |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by luojiebin):

 * owner:  nobody => luojiebin
 * status:  new => assigned


Comment:

 Do this middleware want to do the same thing as the one in Django 1.7
 except that it applies only to view functions, not including those
 middleware modules coming after it? Can you explain it in more detail?
 Thanks.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.9f99886ddae740d3a7d0e95cc7681c69%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.