From 05c6a7a2ef0d6be3a02b8e1a3e2bd2b6afacf799 Mon Sep 17 00:00:00 2001 From: xue <> Date: Fri, 6 Apr 2007 03:06:36 +0000 Subject: Finished blog tutorial day 2. --- .../protected/pages/Day2/ConnectDB.page | 2 +- .../protected/pages/Day2/CreateAR.page | 78 +++++++++++++++++++++ .../protected/pages/Day2/CreateDB.page | 6 +- .../protected/pages/Day2/directories2.gif | Bin 0 -> 6795 bytes 4 files changed, 84 insertions(+), 2 deletions(-) create mode 100644 demos/blog-tutorial/protected/pages/Day2/CreateAR.page create mode 100644 demos/blog-tutorial/protected/pages/Day2/directories2.gif (limited to 'demos/blog-tutorial/protected/pages/Day2') diff --git a/demos/blog-tutorial/protected/pages/Day2/ConnectDB.page b/demos/blog-tutorial/protected/pages/Day2/ConnectDB.page index 232ceb98..90db11ef 100644 --- a/demos/blog-tutorial/protected/pages/Day2/ConnectDB.page +++ b/demos/blog-tutorial/protected/pages/Day2/ConnectDB.page @@ -19,7 +19,7 @@ extension=php_pdo_sqlite.dll

-To further reduce the dependency on the actual database tables, we will also use the Active Record feature which is based on PDO. Each data record will be represented as an Active Record object, which saves us from writing repetitive SQL statements. +To further abstract the actual database tables, we will also use the Active Record (AR) feature. Each data record will be represented as an Active Record object which is capable of performing query, saving and deletion without writing SQL statements.

diff --git a/demos/blog-tutorial/protected/pages/Day2/CreateAR.page b/demos/blog-tutorial/protected/pages/Day2/CreateAR.page new file mode 100644 index 00000000..bf2c05aa --- /dev/null +++ b/demos/blog-tutorial/protected/pages/Day2/CreateAR.page @@ -0,0 +1,78 @@ + + +

Creating Active Record Classes

+ +

+We need to create two Active Record classes, UserRecord and PostRecord, to represent data records in the users and posts tables, respectively. Active Record classes must extend from the base class ActiveRecord, and their properties must match exactly to the fields of the corresponding tables. To better organize our directories, we create a new directory protected/database to hold the class files. +

+ +

+Instead of writing the classes manually, we will use the PRADO command line tool again to generate the classes for us. +

+ +

+Under the blog directory, run the following command to enter into the interactive mode of the command line tool: +

+ + +php path/to/prado-cli.php shell . + + +

+We should see +

+ + +Command line tools for Prado 3.1.0. +** Loaded PRADO appplication in directory "protected". +PHP-Shell - Version 0.3.1 +(c) 2006, Jan Kneschke + +>> use '?' to open the inline help + +>> + + +

+At the prompt, enter the following two commands to create UserRecord and PostRecord classes: +

+ + +>> generate users Application.database.UserRecord + +>> generate posts Application.database.PostRecord + + +

+Here we used the namespace format again to specify the classes to be created. The path Application.database.UserRecord indicates that we want the UserRecord class file to be protected/database/UserRecord.php. +

+ +

+We should see the following directory structure with two new files under protected/database: +

+ + + +

+If we check the UserRecord class file, we should see the following content. As we see, for each field in the users table, the class has a corresponding data member. The constant TABLE specifies the table name for the UserRecord. The static method finder() allows us to perform query and retrieve users data in terms of UserRecord objects, as we will see in later sections. +

+ + +class UserRecord extends TActiveRecord +{ + const TABLE='users'; + public $username; + public $email; + public $password; + public $role; + public $first_name; + public $last_name; + + public static function finder($className=__CLASS__) + { + return parent::finder($className); + } +} + + + \ No newline at end of file diff --git a/demos/blog-tutorial/protected/pages/Day2/CreateDB.page b/demos/blog-tutorial/protected/pages/Day2/CreateDB.page index 0d45ba50..291b20e4 100644 --- a/demos/blog-tutorial/protected/pages/Day2/CreateDB.page +++ b/demos/blog-tutorial/protected/pages/Day2/CreateDB.page @@ -47,7 +47,7 @@ SQLite does not support foreign key

-We use the SQLite command line tool to create the SQLite database. We first create a directory protected/data to hold the SQLite database file. Per SQLite's requirement, this directory and the database file to be created must be set writable by the Web server process. We now execute the following command under the directory protected/data: +We then use the SQLite command line tool to create the SQLite database. We create a directory protected/data to hold the SQLite database file. We now execute the following command under the directory protected/data:

@@ -60,4 +60,8 @@ The database has been created as protected/data/blog.db and we shall se + +It is required by SQLite that both the directory protected/data and the database file protected/data/blog.db be set writable by the Web server process. + + \ No newline at end of file diff --git a/demos/blog-tutorial/protected/pages/Day2/directories2.gif b/demos/blog-tutorial/protected/pages/Day2/directories2.gif new file mode 100644 index 00000000..b053b4c6 Binary files /dev/null and b/demos/blog-tutorial/protected/pages/Day2/directories2.gif differ -- cgit v1.2.3