summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorxue <>2006-11-28 19:04:57 +0000
committerxue <>2006-11-28 19:04:57 +0000
commit50853ea4a6811879a26458e495c46149f7af5313 (patch)
tree4018eda42f86f3cc7ac430c515c0022f4b8b13eb
parent9b4cdb23401bc6f405ff731618110245c9d55b8e (diff)
add description about PDO installation.
-rw-r--r--demos/quickstart/protected/pages/Database/DAO.page3
1 files changed, 3 insertions, 0 deletions
diff --git a/demos/quickstart/protected/pages/Database/DAO.page b/demos/quickstart/protected/pages/Database/DAO.page
index 44da10d5..ec16aec5 100644
--- a/demos/quickstart/protected/pages/Database/DAO.page
+++ b/demos/quickstart/protected/pages/Database/DAO.page
@@ -7,6 +7,9 @@ Data Access Objects (DAO) separates a data resource's client interface from its
<p>
Since version 3.1, PRADO starts to provide a DAO that is a thin wrap around <a href="http://www.php.net/manual/en/ref.pdo.php">PHP Data Objects (PDO)</a>. Although PDO has a nice feature set and good APIs, we choose to implement the PRADO DAO on top of PDO because the PRADO DAO classes are component classes and are thus configurable in a PRADO application. Users can use these DAO classes in a more PRADO-preferred way.
</p>
+<div class="note"><b class="tip">Note:</b>
+Since the PRADO DAO is based on PDO, the PDO PHP extension needs to be installed. In addition, you need to install the corresponding PDO driver for the database to be used in your application. See more details in the <a href="http://www.php.net/manual/en/ref.pdo.php">PHP Manual</a>.
+</div>
<p>
The PRADO DAO mainly consists of the following four classes (in contrast to PDO which uses only two classes, <tt>PDO</tt> and <tt>PDOStatement</tt>):
</p>