In my recent project there was a lot of data business logic, so I had to organize this code somehow. In this article I'll describe a few hints on how to it.
Mixins
Simple business logic functions should in models or managers. When there's a lot of them, the can be split in mixins.
# logic.py
class EventLogic(object):
def start(self):
if self.condition():
# ...
# models.py
class Event(models.Model, EventLogic):
name = models.CharField()
# ...Custom exceptions
For business logic errors you should declare custom exception classes. It's not fun to understand what this specific IntegrityError means.
Generic views
When all logic is in model and can throw, say, BusinessLogicException, we can write views like this:
from django.contrib import messages
def event_action(requets, event_id, action):
# event = get_object_or_404(...)
try:
getattr(event, action)(request.user)
except BusinessLogicException, e:
messages.warning(request, e.message)
return redirect(request.POST.get('next') or event)Subscribe for the news and updates
In this article we'll review general approach to working with the best kind of projects - the ones with old untested and undocumented spaghetti code and a tight schedule. We'll review anger management techniques, coping mechanisms and some refactoring tips that might come in handy.
Protection of WEB App is of paramount importance and it should be afforded the same level of security as the intellectual rights or private property. I'm going to cover how to protect your web app.
There is such a term as Remote Procedure Call (RPC). In other words, by using this technology, programs can call functions on remote computers. There are many ways to implement RPC.
It appears that not everyone knows that in python you can create classes dynamically without metaclasses. I'll show an example of how to do it.So we've learned how to use custom QuerySet to chain requests:Article.objects.old().public()Now we need to make it work for related objects:user.articles.old().public()This is done using use_for_related_fields, but it needs a little trick.
For local project settings, I use old trick with settings_local file:try:from settings_local import \*except ImportError:passSo in settings_local.py we can override variables from settings.py. I didn't know how to supplement them. For example how to add line to INSTALLED_APPS without copying whole list.Yesterday I finally understood that I can import settings from settings_local:# settings_local.pyfrom settings import \*INSTALLED_APPS += (# ...)
Usually users' profiles are stored in single model. When there are multiple user types, separation is made by some field like user_type.Situation is a little more complicated when different data is needed for each user type.In this article I'll describe how I solve this task.