src/sql/SqliteAdapter.php
The class SqliteAdapter has 19 public methods. Consider refactoring SqliteAdapter to keep number of public methods under 10. Open
Open
class SqliteAdapter implements DialectAdapter
{
public function createNamedDB($name)
{
return 'SELECT 1';- Read upRead up
- Exclude checks
TooManyPublicMethods
Since: 0.1
A class with too many public methods is probably a good suspect for refactoring, in order to reduce its complexity and find a way to have more fine grained objects.
By default it ignores methods starting with 'get' or 'set'.
Example
Source https://phpmd.org/rules/codesize.html#toomanypublicmethods
SqliteAdapter has 22 functions (exceeds 20 allowed). Consider refactoring. Open
Open
class SqliteAdapter implements DialectAdapter
{
public function createNamedDB($name)
{
return 'SELECT 1';Avoid unused parameters such as '$name'. Open
Open
public function useNamedDB($name)- Read upRead up
- Exclude checks
UnusedFormalParameter
Since: 0.2
Avoid passing parameters to methods or constructors and then not using those parameters.
Example
class Foo
{
private function bar($howdy)
{
// $howdy is not used
}
}Source https://phpmd.org/rules/unusedcode.html#unusedformalparameter
Avoid unused parameters such as '$charset'. Open
Open
public function setCharSet($charset)- Read upRead up
- Exclude checks
UnusedFormalParameter
Since: 0.2
Avoid passing parameters to methods or constructors and then not using those parameters.
Example
class Foo
{
private function bar($howdy)
{
// $howdy is not used
}
}Source https://phpmd.org/rules/unusedcode.html#unusedformalparameter
Avoid unused parameters such as '$name'. Open
Open
public function createNamedDB($name)- Read upRead up
- Exclude checks
UnusedFormalParameter
Since: 0.2
Avoid passing parameters to methods or constructors and then not using those parameters.
Example
class Foo
{
private function bar($howdy)
{
// $howdy is not used
}
}