Menu
Community /Pin to ProfileBookmark
@NogDogDec 01.2014 — #I personally find the OO syntax clearer than the procedural syntax, but perhaps that's simply because I use it all the time? (And these days I exclusively use PDO.) I don't think the functional syntax is "[I]much[/I] less code"; and even if it's "[I]somewhat[/I] less code", that should be the least of your worries: clear, logical, easy-to-maintain code is much, much more important than saving a few keystrokes, unless perhaps you're writing a small, one-off, throw-away script you don't expect to have to maintain.
IMHO. ?@NogDogDec 01.2014 — #PS: Here's an example of how you can use PDO to do the first query without an inordinate amount of code. Your include file would have something like this:
Your app code for that query could then be:
@NogDogDec 02.2014 — #Thanks, I think I was thinking about two other things when I typed that, while working with code that uses a very different ORM. That's what happens when you don't test your code. ?@NogDogDec 02.2014 — #We use PDO at work, with a PostgreSQL DB, and I'm in the process of learning Laravel PHP framework and its "Eloquent" ORM, along with sort of trying to learn Ruby/Rails* -- so I'm continually confused these days. ?
_____________
PHP + MySqli errors
Hi everyone,
I can’t understand what happens… When I try my site in WAMP, I have the follow errors:
[I]
Deprecated: mysql_query(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO (…)
[I]
Warning: mysql_num_rows() expects parameter 1 to be resource, boolean given in (…)
The same happened with the connect to mysql, but I solved using mysqli extension. But in this case is totally diferent. When I use the [B]mysqli_query [B]mysqli_num_rows[I]“function.mysqli-query doesn’t exist. Closest matches:”
[SIZE=4]
[B][SIZE=5]Someone know solve this problem???
using MySQL
[code=php]<?php
session_start();
if (isset($_SESSION[“manager”])){
header(“location:index.php”);
exit();
}
?>
<?php
if(isset($_POST[“username”])&&isset($_POST[“password”])){
$manager=preg_replace(‘#[^A-Za-z0-9]#i’,”,$_POST[“username”]);
$password=preg_replace(‘#[^A-Za-z0-9]#i’,”,$_POST[“password”]);
$cnn= include “../lojascript/connect_mysql.php”;
$sql=mysql_query($cnn, “SELECT id FROM admin WHERE username=’$manager’ AND password=’$password’ LIMIT 1”);
$existCount=mysql_num_rows($sql);
if ($existCount==1){
while ($row = mysqli_fetch_array($sql)){
$id=$row[“id”];
}
$_SESSION[“id”]=$id;
$_SESSION[“manager”]=$manager;
$_SESSION[“password”]=$password;
header(“location:index.php”);
exit();
}else {
echo ‘Informação incorrecta <a href=”index.php”> Click here</a>’;
exit();
}
}
?>
When I use MySQLi
[code=php]<?php
session_start();
if (isset($_SESSION[“manager”])){
header(“location:index.php”);
exit();
}
?>
<?php
if(isset($_POST[“username”])&&isset($_POST[“password”])){
$manager=preg_replace(‘#[^A-Za-z0-9]#i’,”,$_POST[“username”]);
$password=preg_replace(‘#[^A-Za-z0-9]#i’,”,$_POST[“password”]);
$cnn = include “../lojascript/connect_mysql.php”;
$query= “SELECT id FROM admin WHERE username=’$manager’ AND password=’$password’ LIMIT 1”;
$result= mysqli_query($cnn,$query) or die(mysqli_error());
$num_row = mysqli_num_rows($result);
if ($num_row==1)
{
while ($row = mysqli_fetch_array($result)){
$_SESSION[“id”]=$row[“id”];
}
$_SESSION[“id”]=$id;
$_SESSION[“manager”]=$manager;
$_SESSION[“password”]=$password;
header(“location:index.php”);
exit();
}else {
echo ‘Informação incorrecta <a href=”index.php”> Click here</a>’;
exit();
}
}
?>
Sign in
to post a comment9 Comments(s) ↴
0
@NogDogDec 01.2014 — #I personally find the OO syntax clearer than the procedural syntax, but perhaps that's simply because I use it all the time? (And these days I exclusively use PDO.) I don't think the functional syntax is "[I]much[/I] less code"; and even if it's "[I]somewhat[/I] less code", that should be the least of your worries: clear, logical, easy-to-maintain code is much, much more important than saving a few keystrokes, unless perhaps you're writing a small, one-off, throw-away script you don't expect to have to maintain.IMHO. ?
0
@NogDogDec 01.2014 — #PS: Here's an example of how you can use PDO to do the first query without an inordinate amount of code. Your include file would have something like this:[code=php]
$dsn = 'mysql:dbname=nogdog;host=127.0.0.1';
$user = 'nogdog';
$pwd = 'youwontguess';
$pdo = new PDO($dsn, $user, $pwd);
$pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
[/code]Your app code for that query could then be:
[code=php]
try { // the try/catch structure is not required, but very useful
$sql = 'SELECT id FROM admin WHERE username=:manager AND password=:password LIMIT 1';
$pdo->query($sql, array(
':manager' => $manager,
':password' => $password
));
$existcount = $stmt->rowCount();
}
catch(PDOException $e)
{
// handle DB errors here, e.g.:
error_log("PDO error:".PHP_EOL.var_export($e, 1));
die("Sorry, there was a database error. Debug info has been logged.");
}
catch(Exception $e)
{
// handle any other exceptions here
die("WTF?"); // preferable something "nicer" than that. ;)
}
[/code]0
@NogDogDec 02.2014 — #Thanks, I think I was thinking about two other things when I typed that, while working with code that uses a very different ORM. That's what happens when you don't test your code. ?0
@NogDogDec 02.2014 — #We use PDO at work, with a PostgreSQL DB, and I'm in the process of learning Laravel PHP framework and its "Eloquent" ORM, along with sort of trying to learn Ruby/Rails* -- so I'm continually confused these days. ?_____________