10
85%
develop: 85%

Ran 28 Apr 2017 04:01AM UTC

Files 17

Run time 1s

Badge

Embed ▾

Committed 28 Apr 2017 03:59AM UTC coverage: 68.217% (+0.02%) from 68.197%

Job # DJANGO="Django>=1.10,<1.11"

Build Type

Pull #313

travis-ci

Committed by

web-flow

Commit Message

Remove null from all model fields of type CharField and TextField

Django recommends against using null=True on string-based fields. This
change brings the models in line with Django conventions and suggested
practices. This avoids two different values to represent "empty".

See Django docs for more details:

https://docs.djangoproject.com/en/1.11/ref/models/fields/#null

> Avoid using null on string-based fields such as CharField and
> TextField. If a string-based field has null=True, that means it has
> two possible values for “no data”: NULL, and the empty string. In most
> cases, it’s redundant to have two possible values for “no data;” the
> Django convention is to use the empty string, not NULL.

Pull Request Pull Request #313: Remove null from all model fields of type CharField and TextField

Coverage Stats

1232 of 1806 relevant lines covered (68.22%)

0.68 hits per line

llazzaro / django-scheduler / 550 / 10
85%
develop: 85%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 550.10 (DJANGO="Django>=1.10,<1.11")

llazzaro / django-scheduler / 550 / 10 85% develop: 85%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 550.10 (DJANGO="Django>=1.10,<1.11")

llazzaro / django-scheduler / 550 / 10
85%
develop: 85%

README BADGES
x