Skip to main content

Evil Access

I was thinking today about database APIs when inspiration struck. I ended up hacking out the following class, which I think demonstrates a rather interesting approach to interfacing with a database (interesting enough at least to post here).
class DBQuery implements Iterator
{
protected $_db;
protected $_query;
protected $_result;
protected $_index;
protected $_num_rows;

public function __construct($host, $dbname, $username,
$password) {
$this->_db = new PDO("mysql:dbname=$dbname;host=$host",
$username, $password);
}

public function __get($query) {
$this->_query = $query;
$this->_result = $this->_db->query($query);
return $this->_num_rows = $this->_result->rowCount();
}

public function quote($value) {
return PDO::quote($value);
}

public function __call($query, $values) {
$this->_query = $query;
$this->_result = $this->_db->prepare($this->_query);
$this->_result->execute($values[0]);
return $this->_num_rows = $this->_result->rowCount();
}

public function clear() {
$this->_index = 0;
$this->_num_rows = 0;
$this->_query = '';
$this->_result->closeCursor();
}

public function rewind() {
$this->_index = 0;
}

public function current() {
return $this->_result->fetch(PDO::FETCH_ASSOC,
PDO::FETCH_ORI_ABS, $this->_index);
}

public function key() {
return $this->_index;
}

public function next() {
$this->_index++;
}

public function valid() {
return ($this->_index < $this->_num_rows);
}

public function __toString() {
return $this->_query;
}
}
DBQuery isn't your typical database access class. In fact, I would suggest it's slightly evil since it distorts traditional PHP syntax by abusing taking advantage of three specific PHP features.
  1. PHP allows special characters in an identifier if the string is quoted and is enclosed by {}. So, $myValue and ${"my value"} are both equally valid variable identifiers.

  2. The magic overloading methods allow you handle undefined properties and methods in your class. Specifically, I've made use of __get() and __call().

  3. A class that implements the Iterator interface can be traversed using a foreach loop.
Here's a look at how DBQuery would be used:
// connect to the database
$dbq = new DBQuery("localhost", "test", "dbuser",
"dbpassword");

// query the database if the user is authorized
$username = "administrator";
$password = sha1("password");
if (!$dbq->{"SELECT * FROM admin_user WHERE username=? " .
"AND password=?"}(array($username, $password))) {
die("Unauthorized.");
}

// query the database and display some records
$dbq->{"SELECT id, first_name, last_name FROM employee"};
foreach ($dbq as $result) {
print_r($result);
}

// casting the object as a string yields the query string
echo "Query: $dbq";
Don't try this at home, though, my friends. Just because you can write code like this doesn't mean you should.

Comments

  1. Amazing concept, but I'm afraid if I ever see ANY of this code in production in the future I will be forced to strangle you... Consider yourself warned :)

    ReplyDelete
  2. You could make it even hackier by using func_get_args() in __call so the usage would turn out as

    $dbq->{"SELECT * FROM admin_user WHERE username=? AND password=?"}($username, $password)

    ReplyDelete
  3. Yep this is a pretty cool idea. Wouldn't go as far as Commenter #1, but I think it may be a good idea to not bend the rules this much ;)

    ps: why do I have to log in to comment? I don't want to - please make it possible to comment by just leaving your name =)

    ReplyDelete
  4. this looks pretty neat.
    but I don't understand why you shouldn't use something like this ?
    what rules it bends ?

    ReplyDelete

Post a Comment

Popular posts from this blog

What's Wrong with OOP

Proponents of Object Oriented Programming feel the paradigm yields code that is better organized, easier to understand and maintain, and reusable. They view procedural programming code as unwieldy spaghetti and embrace OO-centric design patterns as the "right way" to do things. They argue objects are easier to grasp because they model how we view the world. If the popularity of languages like Java and C# is any indication, they may be right. But after almost 20 years of OOP in the mainstream, there's still a large portion of programmers who resist it. If objects truly model the way people think of things in the real world, then why do people have a hard time understanding and working in OOP? I suspect the problem might be the focus on objects instead of actions. If I may quote from Steve Yegge's Execution in the Kingdom of Nouns : Verbs in Javaland are responsible for all the work, but as they are held in contempt by all, no Verb is ever permitted to wander about ...

Learning Prolog

I'm not quite sure exactly I was searching for, but somehow I serendipitously stumbled upon the site learnprolognow.org a few months ago. It's the home for an introductory Prolog programming course. Logic programming offers an interesting way to think about your problems; I've been doing so much procedural and object-oriented programming in the past decade that it really took effort to think at a higher level! I found the most interesting features to be definite clause grammars (DCG), and unification. Difference lists are very powerful and Prolog's DCG syntax makes it easy to work with them. Specifying a grammar such as: s(s(NP,VP)) --> np(NP,X,Y,subject), vp(VP,X,Y). np(np(DET,NBAR,PP),X,Y,_) --> det(DET,X), nbar(NBAR,X,Y), pp(PP). np(np(DET,NBAR),X,Y,_) --> det(DET,X), nbar(NBAR,X,Y). np(np(PRO),X,Y,Z) --> pro(PRO,X,Y,Z). vp(vp(V),X,Y) --> v(V,X,Y). vp(vp(V,NP),X,Y) --> v(V,X,Y), np(NP,_,_,object). nbar(nbar(JP),X,3) --> jp(JP,X). pp(pp(PREP,N...

Does Esperanto-USA have a Transparency Problem?

I’ve been an active member of Esperanto-USA for many years, even serving on its board of directors. I wanted to help build a strong, healthy national organization that effectively promotes Esperanto in the United States. But when I stepped down from the board, that desire didn’t end. I continued to bring problems to the attention of the organization, ranging from member rights to strategy to proper governance. I’ve decided to be public about this latest issue because of its seriousness and because of how the board has been secretive about it. The membership deserves to know what is done in their name. What Happened In November 2025, the board of Esperanto-USA sent a formal letter to Esperanto-Ligo en Israelo (ELI) with a copy to UEA, concerning an article published in ELI’s bulletin. The article, written by Eduardo Topol, contained inflammatory political content. And although I agree that the article was extremely offensive, the board’s decision to inj...