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

ICRAR / ngas / 265 / 1
69%
master: 69%

Build:
DEFAULT BRANCH: master
Ran 05 Mar 2019 09:37AM UTC
Files 161
Run time 36s
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

05 Mar 2019 09:26AM UTC coverage: 64.557% (-0.05%) from 64.606%
DB=sqlite3

push

travis-ci

rtobar
NGAS-150 column name matches data in QUERY cmd

For a long time simple 'SELECT * FROM ...' sql commands have been used
to satisfy some of the queries supported by the QUERY command. This of
course means that the order in which columns appear on each row of data
is not predictable, and might not match the column name we associate to
each position.

Historically the QUERY command didn't return the actual names of the
columns being queried, as used "col<N>" as placeholders. This bug is
therefore specific to this new capability, which appeared only in NGAS
11.0.

A unit test has been added that performs a simple check on this aspect.
It does so by assuming that if it finds certain values on a few columns
then column names and values are correctly aligned.

Signed-off-by: Rodrigo Tobar <rtobar@icrar.org>

12386 of 19186 relevant lines covered (64.56%)

0.65 hits per line

Source Files on job 265.1 (DB=sqlite3)
  • Tree
  • List 0
  • Changed 6
  • Source Changed 1
  • Coverage Changed 6
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 250
  • Travis Job 265.1
  • bbdde954 on github
  • Prev Job for DB=sqlite3 on master (#264.1)
  • Next Job for DB=sqlite3 on master (#267.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