Summary - Inspection of "Statement::fetchColumn() will throw an exception i..." - doctrine/dbal - Measure and Improve Code Quality continuously with Scrutinizer

dbal

Failed Conditions

by Sergei

created 2018-12-22 18:45 UTC

The configuration has changed since Scrutinizer has last run. This page might contain changes that are not related to code modifications.

1 failure condition met `elements.rating(<= C).new.exists` Name SQLAnywhere\SQLAnywhereStatement
	2 issues (2 minor) were introduced.
	2 added classes/operations
		A	DBALException::invalidColumnIndex() added
		A	StatementTest::testFetchColumnNonExistingIndex() added
B	↘	C	SQLAnywhereStatement got worse

6.78

▶ ± 0

Test Coverage

78%

▶ ±0%

Head	Sergei Morozov 2018-12-22 18:45 GMT+0000 Merge 2ea917b4884bf9b125ae0f13082b50a4f9e4a9e0 into 7c38e807c8509bdf0c7d35bc8ddb3fb02982bc3f
⋮	1 more commit
Base	Marco Pivetta 2018-12-01 23:51 UTC Merge pull request #3369 from morozov/issues/3366

doctrine / dbal