Hi Tim,
On 11/16/2016 06:23 AM, Tim Graham wrote:
> I took a stab at backwards-compatibility with respect to allowing the
> admin to work without adding 'django.forms' to INSTALLED_APPS. It seems
> to work for at least the simple TEMPLATES = 'BACKEND':
> 'django.template.backends.django.DjangoTemp
If anybody is interested, I created a proof of concept code for PostgreSQL
which extends existing Atomic context:
https://github.com/toudi/django-tpc-proof-of-concept
the actual implementation can be found inside tpc/atomic_tpc.py and there
are two commands available:
./manage.py prepare
./man
This week the Jenkins pull request builders haven't been working correctly,
probably due to an update in Jenkins itself or somewhere else. After
migrating the Jenkins master from Ubuntu 12.04 to 16.04, I started
configuring a different pull request builder plugin that Simon Charette
recommended
Hello,
I'd like to mark my models in some declerative way(meta option, base class)
and make autodetector insert custom migration operations after CreateModel,
DeleteModel.
For this particular use case i have generation of triggers in mind but i
can think of other uses cases when this could be u
Hello,
To be honest I’m pessimistic about the feasibility of emulating transactional
behavior — pretty much the most complicated and low level thing databases do —
in the application. I don’t think that would be considered suitable for Django.
Usually Django handles such cases with a database f
Well, I suppose that it would either lead to very obfuscated implementation
code, or very weird syntax (client code). As for your first argument (
promise that the transaction is unlikely to fail ):
from django.db import distributed:
with distributed('foo') as foo:
MyModel.get_or_create(fie
W dniu piątek, 2 grudnia 2016 12:05:11 UTC+1 użytkownik Mateusz Mikołajczyk
napisał:
>
> What would you say about checking which CRUD operations were executed
> within atomic() call (in order to serialize them and save into a special
> model for databases which don't support this functionality)
What would you say about checking which CRUD operations were executed
within atomic() call (in order to serialize them and save into a special
model for databases which don't support this functionality) ? Is it
realistic?
What I mean by that is that when you do:
from django.db import transact
