GitLab

module_spec, but actually just copy such methods from the original module_spec
into the mock.

remove format_type undefined in module_spec.py from stats-schema.spec

not in the "if" branch as pointed out in the reviewing.

add unit tests of the methods using some dummy spec files with the dummy data of statistics specification
 - getStatisticsSpec()
 - validateStatistics()
 - validateStatistics()
 - check_format()

add include of boost_foreach
update the year of copyright

add some methods for statistics specification
 - getStatisticsSpec()
 - validateStatistics()
 - validateStatistics()

update the year of copyright

addition and modification as a variant of the statistics part of module_spec.py
 - add check_format which checks whether the given element is a valid statistics specification
 - modify check_data_specification to add check of statistics specification
 - add getStatisticsSpec() which returns statistics specification
 - add two of validateStatistics which check whether specified data is valid for statistics specification
 - modify validateItem to add check of item_format in specification

update the year of copyright

 - validate_format
 - check_format
 - validate_format

It checks data types and data format of statistics specification

it pushes contents in statistics category of each spec file.

and modify message string to be compared with in EXPECT_EQ

[trac928] add statistics category and statistics items into some spec files (bob.spec, auth.spec, stats.spec)

This patch from yesterday either disappear or never made it, anyway, recommiting jinmei's code (reviewed on jabber by, er, me)

And update the added code to conform to the new API names

Conflicts:
	src/lib/datasrc/tests/sqlite3_accessor_unittest.cc

There was SQLITE_STATIC for a string that will disappear. This actually
caused a test failure sometimes (for example with MALLOC_CHECK_=2).

(Review on jabber)

Some "Conn" variables were left out and forgotten in previous renames,
fixing what could be found.

discussed via jabber