django-redshift-backend 0.8.1

Note and Limitation

Amazon Redshift doesn’t support RETURNING, so last_insert_id method retrieve MAX(pk) after insertion as a workaround.

refs:

• http://stackoverflow.com/q/19428860

• http://stackoverflow.com/q/25638539

In some case, MAX(pk) workaround does not work correctly. Bulk insertion makes non-contiguous IDs like: 1, 4, 7, 10, … and single insertion after such bulk insertion generates strange id value like 2 (smallest non-used id).

Using sortkey

There is built-in support for this option for Django >= 1.9. To use sortkey, simply define an ordering on the model meta as follow:

class MyModel(models.Model):
    ...

    class Meta:
        ordering = ['col2']

N.B.: there is no validation of this option, instead we let Redshift validate it for you. Be sure to refer to the documentation.

0.8.1 (2018-06-19)

• #38: Fix 0.8 doesn’t compatible with Python 2. Thanks to Benjy Weinberger.

0.8 (2018-06-01)

Incompatible Changes:

• #23,#10 Redshift support time zones in time stamps for migration

  IMPORTANT: With this change, the newly created DateTimeField column will be timestamp with timezone (TIMESTAMPTZ) by migration. Therefore, the existing DateTimeField and the new DateTimeField will have different data types as a redshift schema column type. There are no migration feature by django-redshift-backend. see also: https://github.com/shimizukawa/django-redshift-backend/pull/23

New Features:

• #20,#26: Support for sortkey. Thanks to Maxime Vdb and Kosei Kitahara.

• #24: Add UUIDField support. Thanks to Sindri Guðmundsson.

• #14: More compat with redshift: not use SELECT DISTINCT ON.

Bug Fixes:

• #15,#21: More compat with redshift: not use CHECK. Thanks to Vasil Vangelovski.

• #18: Fix error on migration with django-1.9 or later that raises AttributeError of ‘sql_create_table_unique’.

• #27: annotate() does not work on Django-1.9 and later. Thanks to Takayuki Hirai.

Documentation:

• Add documentation: http://django-redshift-backend.rtfd.io/

0.7 (2017-06-08)

• Drop Python-3.4

• Drop Django-1.7

• Support Python-3.6

• Support Django-1.11

0.6 (2016-12-15)

• Fix crush problem when using bulk insert.

0.5 (2016-10-05)

• Support Django-1.10

• #9: Add support for BigAutoField. Thanks to Maxime Vdb.

• Fix crush problem on sqlmigrate when field modified.

0.4 (2016-05-17)

• Support Python-3.4 and 3.5

• #7: Restore support django-1.7. Version 0.3 doesn’t support django-1.7.

• #4: More compat with redshift: not use SET CONSTRAINTS. Thanks to Maxime Vdb.

• #6: More compat with redshift: not use sequence reset query. Thanks to Maxime Vdb.

• #5: Add REDSHIFT_VARCHAR_LENGTH_MULTIPLIER settings. Thanks to Maxime Vdb.

• Support column type changing on migration.

0.3 (2016-05-14)

• #3: more compat with Redshift (AutoField, DateTimeField, Index). Thanks to Maxime Vdb.

• More compat with redshift: add TextField

• More compat with redshift: not use DEFERRABLE, CONSTRAINT, DROP DEFAULT

• More compat with redshift: support modify column

0.2.1 (2016-02-01)

• “SET TIME_ZONE” warning is changed as debug log for ‘django.db.backend’ logger.

0.2 (2016-01-08)

• Disable “SET TIME_ZONE” SQL execution even if settings.TIME_ZONE is specified.

0.1.2 (2015-06-5)

• Support Django-1.8

0.1.1 (2015-03-27)

• Disable “SELECT FOR UPDATE” SQL execution.

0.1 (2015-03-24)

• Support Django-1.7

• Support “INSERT INTO” SQL execution without “RETURNING” clause.