Re: intoducing dbobj

From: Date: Mon, 30 Jan 2006 22:04:07 +0000
Subject: Re: intoducing dbobj
References: 1 2 3 4  Groups: php.pecl.dev 
Request: Send a blank email to pecl-dev+get-3465@lists.php.net to get a copy of this message
True, I did not dig into PDO, as I thought any layer between me and the DB client lib would mean a lower performance. But now, I can see that PDO more lightweight than what i expected. However I use PQexecParams in crucial parts of the code with binary transmission. And that is something I like, but did not see in PDO (nor did I except from it, its strength is in other areas). So I came to the conclusion that I keep using libpq directly, but thanks to you I also have decided that I will implement the driver for other DBMSs using PDO. I hope this project will reach the state where i can compare the speed of the direct libpq use vs. handling postgreSQL with PDO. Almost forgot: if any of you like the concept I'm implementing, please let me know! I'm seeking for potential use cases I can optimize the code and syntax for. Adam Wez Furlong wrote:
Myth dispelling mode activated... PDO is designed for performance. It's not a DB abstraction layer, it's a data access abstraction layer. PDO will happily let you do this. If you don't want to use PDO, that's fine, just make sure you know what it does or does not do before discounting it; it sounds like you haven't done much research into it. --Wez


« previous php.pecl.dev (#3465) next »