Responding to the original.... On 7/24/08, Ulf Wendel <[EMAIL PROTECTED]> wrote: > > Hi! > > Drizzle aims at the web market but it lacks support for (server-side) > Prepared Statements. How does that work out given the constant move among > the userbase towards Prepared Statements. > > PHP is one of the major players in the web market. Together with PHP 5 a > database access abstraction layer called PDO has been introduced. PDO and > the MySQL driver for PDO (PDO_MYSQL) focus on Prepared Statements: > everything is run as a Prepared Statement. Over the years PDO_MYSQL has > becomes more popular although it suffers both from the status of Prepared > Statements in MySQL and the PDO overall design. Something similar goes for > Connector/J and JDBC. They also focus on Prepared Statements.
Drizzle is aimed at the web market because that's a big target market for "a really really really fast database". Prepared statements != fast. Most target applications will need at least some rewriting of queries and query handling statements; I don't think it's a bad limitation to say "you can't use PDO". Unless a company has a PDO-only policy, I would gather that using a different access abstraction layer is an easier-to-fix problem than "find all the incompatible queries." And if a company *has* a PDO-only policy, then they don't want the speed that Drizzle has. -Sheeri (ps I reserve the right to change my mind when I'm not at the tail end of a conference, tired and hungry.)
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
