As you can see, I’m grouping on the TITLE field. It works exactly as expected, except the summary (and pagination part). It seems like the summary (and pagination) shows all the results without my grouping.
I’m most likely missed something (never went to the 1.1.1 school )
Turned on the logging and it’s clearly showing something …
Querying SQL: SELECT COUNT(*) FROM 'pages' 't'
in /var/www/yii-1.1.1.r1907/framework/zii/widgets/CBaseListView.php (99)
in /var/www/yii-1.1.1.r1907/framework/zii/widgets/CListView.php (151)
in /var/www/yiiki/protected/views/page/index.php (17)
…
Querying SQL: SELECT * FROM 'pages' 't' GROUP BY title ORDER BY created
DESC LIMIT 10
in /var/www/yii-1.1.1.r1907/framework/zii/widgets/CBaseListView.php (99)
in /var/www/yii-1.1.1.r1907/framework/zii/widgets/CListView.php (151)
in /var/www/yiiki/protected/views/page/index.php (17)
This is problematic for me too, except I want to use a custom pager style. I have created a custom pager widget which has different CSS classes and IDs, and I would like to use those classes in the pager generated by the CActiveDataProvider instance.
Which reminds me of another problem… it’s annoying that I have to add another URL rule every time I put a pager in a view to handle the new variable… I might have to create a new thread for that.
But how ugly is that? the reason i use mvc is to seperate my html from logic… I don’t need / want to add another layer of complexity in my views. let alone mixing html in php array’s