I’ve taken that wrapper I talked about in 2012 and re-wrote it https://github.com/ellisgl/GeekLab-GLPDO2

Yii comes with rich features: MVC, DAO/ActiveRecord, I18N/L10N, caching, authentication and role-based access control, scaffolding, testing, etc. It can reduce your development time significantly.

when running any php script from commandline, the full path should always be provided.
the full path should be set before hand inside the application somewhere.

exec(“php-cli $path_to_file > /dev/null 2>/dev/null &”);

Some servers that are configured differently will require the full path to php binary for the shell command to work. How can I get that before hand to ensure compatibility? (obviously asking the host is not possible)

Thanks.

Just one thing on #26: I think there’s a typo on the variable in the query. It should be “INSERT INTO {$table_name} … “

“all file browsers are can work with ftp:// urls making working on live server very easy.”

If you’re working on a live server you’re doing it wrong. Use SVN :)

just my 2 cents as many people / beginners might read this. Need to give them good advice from the start ;)

Reading open source code is not always a good idea…look at wordpress, joomla, phpnuke…code is nearly piece of joke…so choose wisely which u read

You are right with the WHERE clauses for SELECT-Queries, but for INSERT-Queries, you don’t realy need a where clause ;))

The issues with the table names are right, but it’s one of the most important thinks by setting up a databse strukture without table names like that!

To your wrapper:

I don’t realy like Database Classes with queries like that. OOP is great, but I never got the point of this strange and big sql string adapters. Why should it be faster/easier/clearer to use

$objQuery->sql(“SELECT *”)->sql(“FROM TABLE”)->sql(“WHERE foo=bar”)?

Insteat of:

$strQuery = “SELECT * FROM TABLE WHERE foo=bar”;
$objQuery->sql($strQuery);

or

$objQuery->sql(“SELECT * FROM TABLE WHERE foo=bar”);

:))

@Richard: A couple issues with that. Your strKey and strTable are not back ticked and may cause issues, specially if you use table or column names like “name”. Also if you have a WHERE statements, you would have to deal with those. I use a PDO wrapper that allows me to do the following:

class Query_Tablename extends Db_Connect_Dbname
{
public static function getSomethingFromTables($tablename_id = FALSE, $offset = 0, $limit = 10)
{
$SQL = self::statement();

$SQL->sql(‘SELECT tn.*,’)
->sql(‘ tn2.cname’)
->sql(‘FROM `tablename` tn’)
->sql(‘ JOIN `tbalename2` tn2’)
->sql(‘ ON tn2.tablename2_id = tn.tablename_id’)
->sql(‘WHERE (0 = ? OR tn.tablename_id = ?)’)->sBoolInt($tablename_id)->sInt($tablename_id)
->sql(‘LIMIT ? OFFSET ?’)->sInt($limit)->sInt($offset); // use sprintf() functionality, since I need to add the “(int)” stuff.

//$SQL->dump();
return self::selectMany($SQL);
}
}

The wrapper (which isn’t publicly available at this time and I haven’t seen anything like it) does automatic binding, but has a couple issues I need to work out.

agree with your point , and updated the post.

ini_set(‘display_errors’, false);
error_reporting(E_ALL);

Nice argument EllisGL, that’s what I would like to add to this post.

You could build a function to your database class like this:

class MyDatabase {

[…]

insert($strTable, $arData){
if(!is_array($arData) OR count($arData) == 0)
return false;

$strInsertString = “”;
foreach($arData as $strKey => $strValue)
$strInsertString .= $strKey.”='”.$this->real_escape($strValue).”‘,”;
$strInsertString = rtrim($strInsertString, “,”);
return $this->query(“INSERT INTO “.$this->real_escape($strTable).” SET “.$strInsertString);
}
}

backticks are the same as shell_exec

Yes, there are plenty of good tools available on windows too , but linux does have some cool things.
All text editors on linux have code highlighting , all file browsers are can work with ftp:// urls making working on live server very easy.
The terminal is all powerful , with inbuilt ssh , and text editors to directly edit files on server.
File permission system is identical to that of server so problems are caught early , making the code move in the right direction.

INSERT INTO users(name , email , address , phone) VALUES(‘$name’ , ‘$email’ , ‘$address’ , ‘$phone’)”;

would become:

INSERT INTO `users`
SET `name` = ‘$name’,
`email` = ‘$email’,
`address` = ‘$address’,
`phone` = ‘$phone’;

Of course I wouldn’t use this directly. I would use PDO parameterized queries to better protect against SQL injections.