• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

llazzaro / django-scheduler / 657 / 5
85%
develop: 85%

Build:
DEFAULT BRANCH: develop
Ran 02 Jan 2018 01:25PM UTC
Files 17
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

02 Jan 2018 01:24PM UTC coverage: 80.252%. Remained the same
DJANGO="Django>=2.0,<2.1"

Pull #376

travis-ci

web-flow
Convert the text NULL data to the empty string before schema changes

Handling schema changes and data changes should be handled in separate
transactions to avoid pending trigger events.

Fixes the error:

django.db.utils.OperationalError: cannot ALTER TABLE "schedule_event" because it has pending trigger events

From:

https://docs.djangoproject.com/en/2.0/topics/migrations/#data-migrations

> Migrations that alter data are usually called “data migrations”;
> they’re best written as separate migrations, sitting alongside your
> schema migrations.

The previous data migration was implied by the alter operation.

Fixes #361
Pull Request #376: Convert the text NULL data to the empty string before schema changes

1211 of 1509 relevant lines covered (80.25%)

0.8 hits per line

Source Files on job 657.5 (DJANGO="Django>=2.0,<2.1")
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 657
  • Travis Job 657.5
  • 0c8ddf5f on github
  • Prev Job for DJANGO="Django>=2.0,<2.1" on develop (#645.7)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc