I created a step by step guide to Flexviews using Percona Server and Ubuntu 11.10 in a virtual machine

[pick...@gmail.com]

Here is the link:
http://pickettd.github.com/evaluating-flexviews/

Please let me know if this is helpful and/or if you have any
feedback :)

[Justin Swanhart]

Hi,

Sorry it took me so long to reply. I missed your email message.

Your feedback was very helpful. I've fixed all the problems that you noticed.

I was wondering if you might want to take the latest SVN release for a
test ride (please use SVN instead of latest beta)

here is a demo of incremental refresh:
mysql> select * from user_stat_incremental where user_id = 8;
+----------+---------+--------+-------------+----------------+
| mview$pk | user_id | images | gridsquares | last_submitted |
+----------+---------+--------+-------------+----------------+
| 6 | 8 | 589 | 401 | 1105953 |
+----------+---------+--------+-------------+----------------+
1 row in set (0.00 sec)

mysql> delete from geographic.gridimage_base where
gridimage_base.gridimage_id = 1105953;
Query OK, 1 row affected (1.16 sec)

-- THIS ONLY TAKES A FEW SECONDS NOW
mysql> call flexviews.refresh(16,'BOTH',NULL);
Query OK, 0 rows affected (9.64 sec)

-- NOTICE last_submitted WENT DOWN
mysql> select * from user_stat_incremental where user_id = 8;
+----------+---------+--------+-------------+----------------+
| mview$pk | user_id | images | gridsquares | last_submitted |
+----------+---------+--------+-------------+----------------+
| 6 | 8 | 588 | 401 | 1105930 |
+----------+---------+--------+-------------+----------------+
1 row in set (0.00 sec)

[Justin Swanhart]

Hi,

One other thing:

This view is a worst case scenario for Flexviews because you have a
non-distributable aggregate function (max) on the primary key of your
table. This creates a 1:1 "child view" to the base table in order to
maintain the non-distributable aggregate functions. COMPLETE refresh
is probably better than INCREMENTAL in this case.

--Justin