Context Navigation

Changes between Initial Version and Version 1 of Ticket #36101, comment 2

initial	v1
13	13	These database-native bit operations would need to be implemented as lookups and transforms anyway on the ORM side which is something that could be done with `BinaryField` as well.
14	14
15		Given that you can likely implement a `BitField` by subclassing `BinaryField`, overriding it's `db_type` [https://docs.djangoproject.com/en/5.1/howto/custom-model-fields/#useful-methods method] to return `f"bit({self.max_length})"` and that adding a `BitField` in core [https://github.com/disqus/django-bitfield/tree/master while there are third-party alternatives] ~~I'm would incur a significant maintenance burden~~ going to close this ticket as ''wontfix''.
	15	Given that you can likely implement a `BitField` by subclassing `BinaryField`, overriding it's `db_type` [https://docs.djangoproject.com/en/5.1/howto/custom-model-fields/#useful-methods method] to return `f"bit({self.max_length})"` and that adding a `BitField` in core [https://github.com/disqus/django-bitfield/tree/master while there are third-party alternatives] would incur a significant maintenance burden I'm going to close this ticket as ''wontfix''.
16	16
17	17	If you disagree please create a forum discussion to try to form community consensus on the subject [https://docs.djangoproject.com/en/5.1/internals/contributing/writing-code/submitting-patches/#the-django-forum-or-django-developers-mailing-list as documented when proposing new features].