| Conditions | 1 |
| Paths | 1 |
| Total Lines | 74 |
| Code Lines | 62 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 0 | ||
Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.
For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.
Commonly applied refactorings include:
If many parameters/temporary variables are present:
| 1 | <?php |
||
| 71 | protected function getExceptionConversionData() |
||
| 72 | { |
||
| 73 | return array( |
||
| 74 | self::EXCEPTION_CONNECTION => array( |
||
| 75 | array('1044', null, null), |
||
| 76 | array('1045', null, null), |
||
| 77 | array('1046', null, null), |
||
| 78 | array('1049', null, null), |
||
| 79 | array('1095', null, null), |
||
| 80 | array('1142', null, null), |
||
| 81 | array('1143', null, null), |
||
| 82 | array('1227', null, null), |
||
| 83 | array('1370', null, null), |
||
| 84 | array('2002', null, null), |
||
| 85 | array('2005', null, null), |
||
| 86 | ), |
||
| 87 | self::EXCEPTION_FOREIGN_KEY_CONSTRAINT_VIOLATION => array( |
||
| 88 | array('1216', null, null), |
||
| 89 | array('1217', null, null), |
||
| 90 | array('1451', null, null), |
||
| 91 | array('1452', null, null), |
||
| 92 | ), |
||
| 93 | self::EXCEPTION_INVALID_FIELD_NAME => array( |
||
| 94 | array('1054', null, null), |
||
| 95 | array('1166', null, null), |
||
| 96 | array('1611', null, null), |
||
| 97 | ), |
||
| 98 | self::EXCEPTION_NON_UNIQUE_FIELD_NAME => array( |
||
| 99 | array('1052', null, null), |
||
| 100 | array('1060', null, null), |
||
| 101 | array('1110', null, null), |
||
| 102 | ), |
||
| 103 | self::EXCEPTION_NOT_NULL_CONSTRAINT_VIOLATION => array( |
||
| 104 | array('1048', null, null), |
||
| 105 | array('1121', null, null), |
||
| 106 | array('1138', null, null), |
||
| 107 | array('1171', null, null), |
||
| 108 | array('1252', null, null), |
||
| 109 | array('1263', null, null), |
||
| 110 | array('1364', null, null), |
||
| 111 | array('1566', null, null), |
||
| 112 | ), |
||
| 113 | self::EXCEPTION_SYNTAX_ERROR => array( |
||
| 114 | array('1064', null, null), |
||
| 115 | array('1149', null, null), |
||
| 116 | array('1287', null, null), |
||
| 117 | array('1341', null, null), |
||
| 118 | array('1342', null, null), |
||
| 119 | array('1343', null, null), |
||
| 120 | array('1344', null, null), |
||
| 121 | array('1382', null, null), |
||
| 122 | array('1479', null, null), |
||
| 123 | array('1541', null, null), |
||
| 124 | array('1554', null, null), |
||
| 125 | array('1626', null, null), |
||
| 126 | ), |
||
| 127 | self::EXCEPTION_TABLE_EXISTS => array( |
||
| 128 | array('1050', null, null), |
||
| 129 | ), |
||
| 130 | self::EXCEPTION_TABLE_NOT_FOUND => array( |
||
| 131 | array('1051', null, null), |
||
| 132 | array('1146', null, null), |
||
| 133 | ), |
||
| 134 | self::EXCEPTION_UNIQUE_CONSTRAINT_VIOLATION => array( |
||
| 135 | array('1062', null, null), |
||
| 136 | array('1557', null, null), |
||
| 137 | array('1569', null, null), |
||
| 138 | array('1586', null, null), |
||
| 139 | ), |
||
| 140 | self::EXCEPTION_DEADLOCK => array( |
||
| 141 | array('1213', null, null), |
||
| 142 | ), |
||
| 143 | self::EXCEPTION_LOCK_WAIT_TIMEOUT => array( |
||
| 144 | array('1205', null, null), |
||
| 145 | ), |
||
| 149 |
In the issue above, the returned value is violating the contract defined by the mentioned interface.
Let's take a look at an example: