django-sql-tagger 0.3.0

Adds a comment to SQL queries pointing to their place of origin

django-sql-tagger

Adds a comment to SQL queries pointing to their place of origin

Usage

Install:

pip install django-sql-tagger

Configure and add to INSTALLED_APPS in your settings.py file:

INSTALLED_APPS = [
    ...
    'django_sql_tagger',
    ...
]

SQL_TAGGER_CODE_ROOT = BASE_DIR
SQL_TAGGER_PATH_REPLACEMENTS = [
    (r'^myapp/', 'a/'),
]

Settings

SQL_TAGGER_CODE_ROOT - The root of your codebase. This is used to find out which stack frames belong to your application code.

SQL_TAGGER_PATH_REPLACEMENTS - A list of tuples of regular expressions and replacements. This is used to shorten paths in the comments. For example, if you have a file at /myapp/views.py and you want to replace /myapp/ with a/, you would add (r'^myapp/', 'a/') to the list.

Tagging precision

The tagger automatically adds comments to SQL queries, pointing to the place in the code where the query was executed. It tries to be clever in finding the right stack frame. Therefore it ignores all stack frames that don't belong to SQL_TAGGER_CODE_ROOT and anything that subclasses Model or QuerySet.

If you have a utility method that you call from multiple places, you may want to ignore it by adding @django_sql_tagger.ignore_below to the method. This annotation makes django-sql-tagger look only at the stack frames that were created before the annotated method was called.

Tagging transactions

This app monkey-patches transaction.atomic, so no changes to your code are necessary. transaction.atomic now accepts a tag argument, which will be recorded in the comments of the SQL queries. Without a tag, only the filename and line number of the transaction.atomic() call will be recorded.

Example

See the testsite/ directory for an example project using this package.

from django.core.management import BaseCommand
from django.db import connection, transaction

from testapp.models import Website


class Command(BaseCommand):
    def handle(self, *args, **options):
        Website.objects.first()

        with transaction.atomic():
            Website.objects.first()

        with transaction.atomic():
            with transaction.atomic():
                Website.objects.first()

        with transaction.atomic(tag='xxx'):
            Website.objects.first()

The above command executes the following SQL queries:

/* ta/m/c/example.py:10 */ SELECT "testapp_website"."id", "testapp_website"."name", "testapp_website"."url" FROM "testapp_website"; args=(); alias=default
BEGIN;
/* ta/m/c/example.py:12 |> ta/m/c/example.py:13 */ SELECT "testapp_website"."id", "testapp_website"."name", "testapp_website"."url" FROM "testapp_website";
COMMIT;
BEGIN;
SAVEPOINT "s140328319196032_x1";
/* ta/m/c/example.py:15 |> ta/m/c/example.py:16 |> ta/m/c/example.py:17 */ SELECT "testapp_website"."id", "testapp_website"."name", "testapp_website"."url" FROM "testapp_website";
RELEASE SAVEPOINT "s140328319196032_x1";
COMMIT;
BEGIN;
/* T=xxx ta/m/c/example.py:19 |> ta/m/c/example.py:20 */ SELECT "testapp_website"."id", "testapp_website"."name", "testapp_website"."url" FROM "testapp_website";
COMMIT;

The comments make it easier to identify where the SQL queries are coming from, for example when you see the query in the database log or a database monitoring tool.

License

GPLv3 (see LICENSE file)

Changelog

0.2.1

• Fix AttributeError: type object 'Command' has no attribute 'code'

0.2.0

• Monkey-patch transaction.atomic so all transactions are tagged by default

0.1.0

Initial release

Development

Install dependencies

pip install -e '.[dev]'

Run tests

cd testsite/
pytest

Release

1. Update changelog in this file.
2. Wait for tests to pass.
3. Create a new release on GitHub. This will trigger a new job that will publish the package to PyPI.