tickets: 2417
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2417 | 2006-07-24 23:17:20 | 2013-05-29 07:58:25 | 2022-03-06 03:25:57.189026 | Ready for checkin | closed | Database layer (models, ORM) | New feature | Normal | dev | fixed | Support for binary type fields (aka: bytea in postgres and VARBINARY in mysql) | I have a need of having fields that store small blips of binary information. In general this works fine with the CharField, however it will not work for all such fields. For example a datum that is just the NUL character, or a series of NUL characters. With postgres at least: "Character strings disallow zero octets," These are not things like images or other such large amounts of data. They are typically fairly short (10 to 200 bytes). For my purposes I created a small patch that adds a new field type that basically is a CharField except it uses the binary type on postgres and mysql. Does the django project plan on supporting a binary type field, if so should I post my patch for this? | scanner@nominum.com | 0 | 1 | 0 | 0 | 0 | 0 |