Changes between Initial Version and Version 1 of Ticket #27446


Ignore:
Timestamp:
Nov 5, 2016, 9:41:20 AM (8 years ago)
Author:
Ben Cole
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #27446

    • Property Owner changed from nobody to Ben Cole
    • Property Status new → assigned

  • Ticket #27446 – Description

    initial v1  
     1There exist multiple use cases where a database will generate values for a field/column. Most RDBMSes expect that these columns be excluded from from `INSERT` and `UPDATE` statements. However they still need to be included in `SELECT` statements.
     2
     3The proposal therefore is to add a `readonly` option to the base `Field` class that when `True` would strip these fields from being compiled to SQL during `INSERT`s and `UPDATE`s. This allows for a very simple change that covers all possible write queries that Django may perform (including bulk_*).
     4
     5There exists a proof of concept https://github.com/novafloss/django-readonly-field
Back to Top