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

hypothesis / h / 8306 / 1
97%
master: 97%

Build:
DEFAULT BRANCH: master
Ran 01 Oct 2015 11:07AM UTC
Files 84
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

01 Oct 2015 10:59AM UTC coverage: 66.638%. Remained the same
8306.1

push

travis-ci

nickstenning
Make sqlalchemy ignore old columns on INSERT/SELECT/UPDATE

These columns are going to be removed shortly. In 25ae155 we made them
nullable, in the hope that this would stop sqlalchemy from attempting to
set values in these columns. Unfortunately, that doesn't do it:
sqlalchemy continues to send explicit NULL values to these columns.

In order to get sqlalchemy to completely ignore these unused columns on
INSERT, on UPDATE and on SELECT, we have to:

- mark the `server_default` and `server_onupdate` values to be
  `FetchedValue()` -- this is usually used when a field is updated
  server-side by a trigger, and suppresses inclusion of the field in
  INSERTs and UPDATEs respectively:

  http://docs.sqlalchemy.org/en/rel_1_0/core/defaults.html#sqlalchemy.schema.FetchedValue

- mark the entire column as deferred, to prevent eager loading of these
  column values on SELECT:

  http://docs.sqlalchemy.org/en/rel_1_0/orm/loading_columns.html#deferred-column-loading

2333 of 3501 relevant lines covered (66.64%)

0.67 hits per line

Source Files on job 8306.1
  • Tree
  • List 0
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 8306
  • Travis Job 8306.1
  • 15ec1529 on github
  • Prev Job for on master (#8304.1)
  • Next Job for on master (#8309.1)
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