<?php
class Product extends CActiveRecord
{
    /**
     * The followings are the available columns in table 'Product':
     * @var integer $id
     * @var integer $brandId
     * @var string $name
     * @var string $price
     */
 
    /**
     * Returns the static model of the specified AR class.
     * @return CActiveRecord the static model class
     */
    public static function model($className=__CLASS__)
    {
        return parent::model($className);
    }
 
    /**
     * @return string the associated database table name
     */
    public function tableName()
    {
        return 'Product';
    }
 
    /**
     * @return array validation rules for model attributes.
     */
    public function rules()
    {
        return array(
            array('name','length','max'=>255),
            array('price','length','max'=>8),
            array('name, price', 'required'),
        );
    }
 
    /**
     * @return array relational rules.
     */
    public function relations()
    {
        // NOTE: you may need to adjust the relation name and the related
        // class name for the relations automatically generated below.
        return array(
            'brand' => array(self::BELONGS_TO, 'Brand', 'brandId'),
            'categories' => array(self::MANY_MANY, 'Category', 'ProductCategory(productId, categoryId)'),
        );
    }
 
    /**
     * @return array customized attribute labels (name=>label)
     */
    public function attributeLabels()
    {
        return array(
            'id'=>'Id',
            'brandId'=>'Brand',
            'name'=>'Name',
            'price'=>'Price',
        );
    }
}

Enable your weblogger: this you will find in: /yourProject/protected/config/main.php

By default your log array looks something like this: (Tip: IF you haven’t done this, and you find it hard to find you way in the file, comment everything you deem meaningful, use spaces and limit blocks of codes with comment of your choice)

        'log'=>array(
            'class'=>'CLogRouter',
            'routes'=>array(
                array(
                    'class'=>'CFileLogRoute',
                    'levels'=>'error, warning',
                ),
            ),
        ),

Let’s add in the CWebLogRoute so it looks like this.

  'log'=>array(
            'class'=>'CLogRouter',
            'routes'=>array(
                array(
                    'class'=>'CFileLogRoute',
                    'levels'=>'error, warning',
                ),
                array(
                    'class'=>'CWebLogRoute',
                    'levels'=>'trace,info, error, warning',
                ),
            ),
        ),

Visit the application and notice that at the bottom of the screen a table is shown displaying everything Yii does to make it possible for the website to be shown correctly. This is especially useful when you’re new to the Yii DB stuff.

Let’s start by getting all of our products. If you are trying this tutorial, then please create a simple new installation, config the database settings in /protected/config/main.php and create your database with the proposed columns from the model seen earlier.

You can test this in any controller, because the system already has a default SiteController in: /protected/controllers/siteController.php, this tutorial will use siteController.php with the view-file in: /protected/views/site/index.php

So we’ll first modify our SiteController::actionIndex method.

    public function actionIndex()
    {
        $this->render('index', array(
            'Products' => Product::model()->findAll(),
        ));
    }

Open the view-file related to the actionIndex() The system has an array that will be passed to our index view. This array contains ‘Products’ which will be usable as ‘$Products’ in our view: /protected/views/site/index.php

<?php $this->pageTitle=Yii::app()->name; ?>
 
<h1>
    Welcome, <?php echo Yii::app()->user->name; ?>!
</h1>
<table>
<?php foreach($Products AS $Product):?>
    <tr>
        <td><?php echo $Product->name;?></td>
        <td><?php echo $Product->price;?></td>
    </tr>
<?php endforeach;?>
</table>

The system (Yii) writes the SQL statements for us thanks to the AR and everything behind that, but we got back an array of product objects.

Now let’s use the ‘brand’ relation that is set in our Product model.

Without changing the controller, we can simply change the view and add the line to output the brand name.

<td><?php echo $Product->brand->name;?></td>

Now how did Yii do that? Look at the screen logger. You will see that it used the ‘lazy-loading’ technique to query the Brand table at that point.

Querying SQL: SELECT * FROM `Product`
 
Querying SQL: SELECT `Product`.`id` AS `t0_c0`, t1.`id` AS `t1_c0`,
t1.`name` AS `t1_c1`, t1.`website` AS `t1_c2` FROM `Product` LEFT OUTER
JOIN `Brand` t1 ON (`Product`.`brandId`=t1.`id`) WHERE (`Product`.`id`=3)
 
Querying SQL: SELECT `Product`.`id` AS `t0_c0`, t1.`id` AS `t1_c0`,
t1.`name` AS `t1_c1`, t1.`website` AS `t1_c2` FROM `Product` LEFT OUTER
JOIN `Brand` t1 ON (`Product`.`brandId`=t1.`id`) WHERE (`Product`.`id`=4)

This is not the best way to go so let’s change the actionIndex in siteController.php

    public function actionIndex()
    {
        // renders the view file 'protected/views/site/index.php'
        // using the default layout 'protected/views/layouts/main.php'
        $this->render('index', array(
            'Products' => Product::model()->with(array('brand'))->findAll(),
        ));
    }

One query is all that is needed for all the data to be collected.

Querying SQL: SELECT `Product`.`id` AS `t0_c0`, `Product`.`brandId` AS
`t0_c1`, `Product`.`name` AS `t0_c2`, `Product`.`price` AS `t0_c3`, t1.`id`
AS `t1_c0`, t1.`name` AS `t1_c1`, t1.`website` AS `t1_c2` FROM `Product` 
LEFT OUTER JOIN `Brand` t1 ON (`Product`.`brandId`=t1.`id`)

The view file does not have to change for this. This technique is called eager-loading and has advantages over lazyloading sometimes.

This tutorial is a modified tutorial from another website/blog that unfortunantly isn’t online anymore, domain is being sold by godaddy.com, so I search my archives to retrieve this on, and post him here, hence a few additions, deletes and rewrites from me.

Share on Facebook

There are a few ways to add to a models that increase code re-usability. One way is to just add methods to the models, methods which can execute complex queries and make your controller thinner.

The first example, a query that will get all products within a price range, it will need a limit and an offset for pagination, so in the Products model, the following function can be added:

public function findAllByPrice($min=0, $max=1000000, $offset = 0, $limit = 30) {
    $Criteria = new CDbCriteria();
    $Criteria->condition = "price >= :min AND price <=:max";
    $Criteria->limit = $limit;
    $Criteria->offset = $offset;
    $Criteria->params = array ( ':min' => $min, ':max' => $max );
    return $this->with(array('brand'))->findAll($Criteria);
}

Now in any of the controlller files this method can be easily accessed and returns all of the ‘Product’ objects with a single line command:

$Products = Product::model()->findAllByPrice(100, 700, 0, 30);

Another way to do the same is to:

public function getProducts($category){
    return $this->findAll('categoryIdFk=:category', array(':category'=>$category));
}

Let’s implement the first query using two named scope methods that I’ll create.

// Price Between - Named Scope ---------------------------------//
public function scopePriceBetween($min, $max) {
    $Criteria = new CDbCriteria();
    $Criteria->condition = "$this->tableName().price BETWEEN :min AND :max";
    $Criteria->params = array(':min' => $min,   ':max' => $max);
    $this->getDbCriteria()->mergeWith($Criteria);
    return $this;
}

Now an additional named scope for the limit element

//  Limit - Named Scope --------------------------------------//
public function scopeLimit($limit = 30, $offset = 0) {
    $Criteria = new CDbCriteria();
    $Criteria->limit = $limit;
    $Criteria->offset = $offset;
    $this->getDbCriteria()->mergeWith($Criteria);
    return $this;
}

Now we can simply use our named scopes to get our data back, and then we could continue to pile on named scopes to return our data.

$Products = Product::model()->scopePriceBetween(0, 5000) ->scopeLimit(30, 1)->findAll();

The query that actually gets executed is simple and looks like this:

SELECT * FROM `Product` WHERE Product.price BETWEEN :MIN AND :MAX LIMIT 30 OFFSET 1

This tutorial is a modified tutorial from another website/blog that unfortunantly isn’t online anymore, domain is being sold by godaddy.com, so I search my archives to retrieve this on, and post him here, hence a few additions, deletes and rewrites from me.

Share on Facebook

Brake down the configuration file in multiple files, this will give you some speed disadvantage and some will  saying that I’m raping Yii framework purpose for speed but at least to me it seems more clear

This is the protected.config/main.php

dirname(__FILE__).DIRECTORY_SEPARATOR.'..',
'name'=>'WEBSITENAME',
'modules'=>array(
'users'=>array(
//sub modules in the module users
'modules'=>array(
'messaging',
'profile',
'dashboard',
)
),
'about',
'forums',
),
// preloading 'log' component active loading
'preload'=>array('log'),

// autoloading model and component classes lazy loading
// I make the difference between CformModel and CActiveRecord
'import'=>array(
'application.models.*',
'application.models.forms.*',
'application.models.database.*',
),

// application components
'components'=>array(
// enable cookie-based authentication
'user'=>array('allowAutoLogin'=>true),

// data relinquished to database.php
// for easy access and usability as also for the future
// installation procedure, it's less to write to a file
'db'=>include(dirname(__FILE__).'/database.php'),

// for a better overview we exculded url routes to a seperate file
'urlManager'=>include(dirname(__FILE__).'/routes.php'),

//authentication component needs data from db for CdbConnection
'authManager'=>array(
'class'=>'CDbAuthManager',
'connectionID'=>'db',
'defaultRoles'=>array('authenticated', 'guest'),
),

//security measures
'request'=>array(
'enableCsrfValidation'=>true,
'enableCookieValidation'=>true,
),
),

// application-level parameters that can be accessed
// using Yii::app()->params['paramName']
// uncomment the following if you want static params in the application
//'params'=>array(include(dirname(__FILE__).'/params.php'))
);

database.php

'CDbConnection',
'connectionString'=>'mysql:host=localhost;dbname=mysql',
//'connectionString'=>'pgsql:host=localhost;port=5432;dbname=mysql',
'username' => 'root',
'password' => '',
);
?>

routes.php

'path', // path or get
'urlSuffix' => '', //.html .whateverextentionyouwant
'showScriptName' => true,
'rules'=>array(
'users/recovery/perimeterSecurity/'=>'users/recovery/perimeterSecurity',
),
);
?>

param.php

//nothing in it at the moment

Share on Facebook

A) They make things complicated

B) Subject you to some nasty code stuff and rules

C) Because templating and Frameworks can be water and fire.

Codeigniter on the opposite has some advantage on it side for the templating stuff. This is really a short explanation for a common problem in other framework.

What to do if you want a nice folder structure or have different template styles, remember this is just a basic thing which happen to work in CI 1.7.


function index(){
$this->load->view('Themename/news/index);
}

Just add some slashes an it works so normally it should work if you would make an adaptation for themes too with a variable in it.

The next thing was kind of hard to find on the web so let me share it. It’s for when you develop with CI and your not working in the root directory of your server.


DirectoryIndex index.php
RewriteEngine on
RewriteCond $1 !^(index\.php|images|css|js|robots\.txt|favicon\.ico)
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ ./index.php/$1 [L,QSA]

Share on Facebook

Share on Facebook

Share on Facebook