This project does not seem to handle request data directly as such no vulnerable execution paths were found.
include
, or for example
via PHP's auto-loading mechanism.
These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
|||||||||||
2 | /** |
|||||||||||
3 | * This is an old PHP4 database abstraction class. It has be rewritten to use |
|||||||||||
4 | * a singleton of PEARs MDB2. |
|||||||||||
5 | */ |
|||||||||||
6 | require_once 'MDB2.php'; |
|||||||||||
7 | ||||||||||||
8 | class DB_Sql |
|||||||||||
9 | { |
|||||||||||
10 | var $db; |
|||||||||||
11 | var $row; |
|||||||||||
12 | var $result; |
|||||||||||
13 | ||||||||||||
14 | function DB_Sql($dbhost = '', $dbuser = '', $dbpass = '', $dbname = '') |
|||||||||||
0 ignored issues
–
show
Coding Style
Best Practice
introduced
by
![]() |
||||||||||||
15 | { |
|||||||||||
16 | if (empty($dbhost) OR empty($dbuser) OR empty($dbpass) OR empty($dbname)) { |
|||||||||||
0 ignored issues
–
show
Comprehensibility
Best Practice
introduced
by
Using logical operators such as
or instead of || is generally not recommended.
PHP has two types of connecting operators (logical operators, and boolean operators):
The difference between these is the order in which they are executed. In most cases,
you would want to use a boolean operator like Let’s take a look at a few examples: // Logical operators have lower precedence:
$f = false or true;
// is executed like this:
($f = false) or true;
// Boolean operators have higher precedence:
$f = false || true;
// is executed like this:
$f = (false || true);
Logical Operators are used for Control-FlowOne case where you explicitly want to use logical operators is for control-flow such as this: $x === 5
or die('$x must be 5.');
// Instead of
if ($x !== 5) {
die('$x must be 5.');
}
Since // The following is currently a parse error.
$x === 5
or throw new RuntimeException('$x must be 5.');
These limitations lead to logical operators rarely being of use in current PHP code. ![]() |
||||||||||||
17 | $this->db = MDB2::singleton(DB_DSN); |
|||||||||||
18 | } else { |
|||||||||||
19 | $this->db = MDB2::singleton('mysql://' . $dbuser . ':' . $dbpass . '@' . $dbhost . '/' . $dbname); |
|||||||||||
20 | } |
|||||||||||
21 | ||||||||||||
22 | if (PEAR::isError($this->db)) { |
|||||||||||
23 | die($this->db->getMessage() . ' ' . $this->db->getUserInfo()); |
|||||||||||
0 ignored issues
–
show
The method
DB_Sql() contains an exit expression.
An exit expression should only be used in rare cases. For example, if you write a short command line script. In most cases however, using an ![]() |
||||||||||||
24 | } |
|||||||||||
25 | $this->db->query('SET NAMES utf8'); |
|||||||||||
26 | $this->db->setOption('portability', MDB2_PORTABILITY_NONE); |
|||||||||||
27 | } |
|||||||||||
28 | ||||||||||||
29 | View Code Duplication | function query($SQL) |
||||||||||
0 ignored issues
–
show
This method seems to be duplicated in your project.
Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation. You can also find more detailed suggestions in the “Code” section of your repository. ![]() |
||||||||||||
30 | { |
|||||||||||
31 | $this->result = $this->db->query($SQL); |
|||||||||||
32 | if (PEAR::isError($this->result)) { |
|||||||||||
33 | die($this->result->getMessage() . ' ' . $this->result->getUserInfo()); |
|||||||||||
0 ignored issues
–
show
The method
query() contains an exit expression.
An exit expression should only be used in rare cases. For example, if you write a short command line script. In most cases however, using an ![]() |
||||||||||||
34 | } |
|||||||||||
35 | } |
|||||||||||
36 | ||||||||||||
37 | View Code Duplication | function exec($SQL) |
||||||||||
0 ignored issues
–
show
This method seems to be duplicated in your project.
Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation. You can also find more detailed suggestions in the “Code” section of your repository. ![]() |
||||||||||||
38 | { |
|||||||||||
39 | $this->result = $this->db->exec($SQL); |
|||||||||||
40 | if (PEAR::isError($this->result)) { |
|||||||||||
41 | die($this->result->getMessage() . ' ' . $this->result->getUserInfo()); |
|||||||||||
0 ignored issues
–
show
The method
exec() contains an exit expression.
An exit expression should only be used in rare cases. For example, if you write a short command line script. In most cases however, using an ![]() |
||||||||||||
42 | } |
|||||||||||
43 | ||||||||||||
44 | $this->result->free(); |
|||||||||||
45 | } |
|||||||||||
46 | ||||||||||||
47 | View Code Duplication | function nextRecord() |
||||||||||
0 ignored issues
–
show
This method seems to be duplicated in your project.
Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation. You can also find more detailed suggestions in the “Code” section of your repository. ![]() |
||||||||||||
48 | { |
|||||||||||
49 | // Gennemsøger recordset. |
|||||||||||
50 | // Går videre til næste post hver gang den kaldes. |
|||||||||||
51 | // Returnere true så længe der er en post |
|||||||||||
52 | // while($db->next_record()) { |
|||||||||||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
73% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. ![]() |
||||||||||||
53 | $this->row = $this->result->fetchRow(MDB2_FETCHMODE_ASSOC); |
|||||||||||
54 | if (PEAR::isError($this->row)) { |
|||||||||||
55 | die($this->row->getMessage() . '' . $this->row->getUserInfo()); |
|||||||||||
0 ignored issues
–
show
The method
nextRecord() contains an exit expression.
An exit expression should only be used in rare cases. For example, if you write a short command line script. In most cases however, using an ![]() |
||||||||||||
56 | } |
|||||||||||
57 | ||||||||||||
58 | return($this->row); |
|||||||||||
59 | } |
|||||||||||
60 | ||||||||||||
61 | function affectedRows() |
|||||||||||
62 | { |
|||||||||||
63 | // returnere antallet af berørte rækker ved INSERT, UPDATE, DELETE |
|||||||||||
64 | // print($db->affected_rows()); |
|||||||||||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
80% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. ![]() |
||||||||||||
65 | ||||||||||||
66 | return($this->db->_affectedRows(NULL)); |
|||||||||||
0 ignored issues
–
show
|
||||||||||||
67 | } |
|||||||||||
68 | ||||||||||||
69 | function f($name) |
|||||||||||
70 | { |
|||||||||||
71 | // Returnere værdien fra feltet med navet som er angivet. |
|||||||||||
72 | // Print($db->f("felt")); |
|||||||||||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
82% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. ![]() |
||||||||||||
73 | return($this->row[$name]); |
|||||||||||
74 | } |
|||||||||||
75 | ||||||||||||
76 | function free() |
|||||||||||
77 | { |
|||||||||||
78 | // Frigør hukommelse til resultatet |
|||||||||||
79 | // $db->free(); |
|||||||||||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
72% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. ![]() |
||||||||||||
80 | $this->result->free(); |
|||||||||||
81 | } |
|||||||||||
82 | ||||||||||||
83 | function insertedId() |
|||||||||||
84 | { |
|||||||||||
85 | // Returnere det id som lige er blevet indsat |
|||||||||||
86 | // $sidste_id = $db->inserted_id(); |
|||||||||||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
55% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. ![]() |
||||||||||||
87 | ||||||||||||
88 | return($this->db->lastInsertID()); |
|||||||||||
89 | } |
|||||||||||
90 | ||||||||||||
91 | function numRows() |
|||||||||||
92 | { |
|||||||||||
93 | // Returnere antallet af rækker |
|||||||||||
94 | // print($db->num_rows()); |
|||||||||||
0 ignored issues
–
show
Unused Code
Comprehensibility
introduced
by
80% of this comment could be valid code. Did you maybe forget this after debugging?
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. ![]() |
||||||||||||
95 | ||||||||||||
96 | return($this->result->numRows()); |
|||||||||||
97 | } |
|||||||||||
98 | ||||||||||||
99 | function escape($value) |
|||||||||||
100 | { |
|||||||||||
101 | return mysql_escape_string($value); |
|||||||||||
0 ignored issues
–
show
The function
mysql_escape_string() has been deprecated with message: Deprecated as of PHP 5.3.0. Relying on this feature is highly discouraged (use mysql_real_escape_string() instead).
This function has been deprecated. The supplier of the file has supplied an explanatory message. The explanatory message should give you some clue as to whether and when the function will be removed from the class and what other function to use instead. ![]() |
||||||||||||
102 | } |
|||||||||||
103 | ||||||||||||
104 | function quote($value, $type) |
|||||||||||
105 | { |
|||||||||||
106 | return $this->db->quote($value, $type); |
|||||||||||
107 | } |
|||||||||||
108 | } |
|||||||||||
109 |