tickets: 811
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 811 | 2005-11-16 05:59:24 | 2011-06-25 16:58:33 | 2022-03-06 03:21:42.880199 | Ready for checkin | closed | Core (Other) | New feature | Normal | dev | fixed | IPv6 address field support | Hi the attached patch adds a new field called IP6AddressField that allows the entry of IPv6 addresses. It has a validator too called isValidIPAddress6 and I've also added another validator called isValidIPAddress that checks whether an address is IPv4 or IPv6. Tested on postgres backend. I initially did this as a replacement for the existing IPAddressField but it breaks backward compatibility because all the non-postgres backends have to have their fields sizes increased. It's up to you whether you want to do this or not. | erikr | mattimustang@gmail.com | ipv6 IPAddressField dceu2011 | 0 | 1 | 0 | 0 | 0 | 0 |