The it’s-all-a-dream interpretation is the only one that makes sense from a science-fiction point-of-view, however unsatisfying it is from a critical perspective. The slightly wobbling top at the end points, rather overtly, to the real answer: it’s meant to be ambiguous.

That said: WTF? We’ve got to bring down a company on the verge of being The Most Powerful Corporation in the World. So let’s use this highly radical, unproven and improbable, voodoo-science inception approach. Oh, and by the way, we have to plant a mole within the highest ranks of the multinational beast within the next, say, two weeks, so we can get valuable information that is necessary to penetrate and manipulate the fragile psyche of our target.

Cut-scene: it’s done. This is logic that only makes sense within the context of a dream. The sort of dream Coleridge, or Rube Goldberg, would have.

Science generally favors the application of Occam’s Razor: buy the airline and crash the damn plane with the kid on it. Or just send in the ninjas. The ensuing infighting among the various executive factions vying for the top spot after junior is out of the picture will ensure that any plans Acme Energy Inc had for world domination are put off course indefinitely.

Inception was entertaining. But Memento was a more interesting film intellectually. That’s a film that truly merited this kind of philosophical scrutiny. Remember Sammy Jankis.

This was in support of the basic premise: Inception isn’t science fiction

Google Fonts API

I have to look at it in Google Chrome to see the effects. Also, don’t forget my old CSS font families page:

Favorite CSS Font Families

An example:
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Cache-Control: no-cache
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Content-Encoding: gzip
X-AppEngine-Estimated-CPM-US-Dollars: $0.000164
X-AppEngine-Resource-Usage: ms=11 cpu_ms=0 api_cpu_ms=0
Date: Sat, 24 Apr 2010 20:28:51 GMT
Server: Google Frontend
Content-Length: 299

Very interesting. I have not seen this mentioned before. But apparently it’s been around for a while.

On top of that, I (somewhat deliberately) broke the email on my server, so I wasn’t getting notified of any comments. Still need to configure wordpress to use gmail. But at least the comments appear now to be working properly.

Next, this plugin should come standard issue with WordPress. I know the keys are a bit of a hassle. But WordPress should offer something out or the box, because the amount of spam I get through the comment forms on this site is demoralizing.

Anyway, easy to install and well worth the effort, I hope. Find reCAPTCHA installation notes here:

http://wordpress.org/extend/plugins/wp-recaptcha/installation/

Now, let’s see if this thing works.

    function query_bottom_count($bottom_value, $start_uts, $end_uts)
    {
        $sql = <<<XSQL
SELECT
    REPLACE( SUBSTRING_INDEX( SUBSTRING_INDEX( last_result_url,
        '://', -1 ) , '/', 1 ) , 'www.', '' ) AS domain,
    COUNT( REPLACE( SUBSTRING_INDEX( SUBSTRING_INDEX( last_result_url, '://', -1 ) ,
        '/', 1 ) , 'www.', '' ) ) AS hits
FROM queries as Query
WHERE insert_uts >= ?
AND insert_uts < ?
GROUP BY domain HAVING hits = ?;
XSQL;

        $ParamList = array($start_uts, $end_uts, $bottom_value);
        $Data = $this->query($sql, $ParamList);
        if ( !$Data ) return 0;
        return count($Data);
    }

Just setting the record straight.

Cake Core Bugs

There are a couple documented bugs that still outstanding as of release 1.2.4.8284. If you are doing anything more than basic testing, one of these could bite you eventually:

https://trac.cakephp.org/ticket/6205
https://trac.cakephp.org/ticket/6468

Here is a patch file that fixes them:

# Fix issues with CakePhp model unit tests
# Tom at klenwell@gmail.com
# CakePhp Version: 1.2.4.8284

diff -r ead5d3b62da7 -r df04a99fec1b cake/libs/model/datasources/dbo_source.php
--- a/cake/libs/model/datasources/dbo_source.php	Mon Aug 10 21:16:09 2009 -0700
+++ b/cake/libs/model/datasources/dbo_source.php	Mon Sep 14 21:08:12 2009 -0700
@@ -2355,6 +2355,15 @@ class DboSource extends DataSource {
 			$column['default'] = null;
 		}

+                // solves fixture problem
+                // see https://trac.cakephp.org/ticket/6205
+                if (($column['type'] == 'datetime' || $column['type'] == 'timestamp' ) && isset($column['default']) && $column['default'] === '') {
+                    $column['default'] = null;
+                }
+                if ( $column['type'] == 'timestamp' && $column['default'] === 'CURRENT_TIMESTAMP' )
+                    #pr($column);
+                    $column['default'] = null;
+
 		if (isset($column['key']) && $column['key'] == 'primary' && $type == 'integer') {
 			$out .= ' ' . $this->columns['primary_key']['name'];
 		} elseif (isset($column['key']) && $column['key'] == 'primary') {
@@ -2455,4 +2464,4 @@ class DboSource extends DataSource {
 		return 'string';
 	}
 }
-?>
\ No newline at end of file
+?>

diff -r ead5d3b62da7 -r df04a99fec1b cake/tests/lib/cake_test_fixture.php
--- a/cake/tests/lib/cake_test_fixture.php	Mon Aug 10 21:16:09 2009 -0700
+++ b/cake/tests/lib/cake_test_fixture.php	Mon Sep 14 21:08:12 2009 -0700
@@ -114,7 +114,12 @@ class CakeTestFixture extends Object {
 			}
 		}

-		if (!isset($this->table)) {
+                // solves HABTM problem
+                // see https://trac.cakephp.org/ticket/6468
+                if (isset($model->table)) {
+                        $this->table = $model->table;
+                }
+                elseif (!isset($this->table)) {
 			$this->table = Inflector::underscore(Inflector::pluralize($this->name));
 		}

@@ -190,4 +195,4 @@ class CakeTestFixture extends Object {
 		return $return;
 	}
 }
-?>
\ No newline at end of file
+?>

Fixtures

The design and usage of fixtures still seems fickle. For instance, the CakePhp docs and packaged test examples promote the explicit declaration of fields in fixtures. I find this tedious. Happily, it is also unnecessary, thanks to the import property.

To avoid this nuisance, use the import ‘model’ or ‘table’ setting to automatically load the table schema from the existing database. See the example here:

simple_record_fixture.php

A couple other tips for using fixtures:

1. Import all fixtures associated with a model in the unit test for that model
2. If unit testing a plugin, the value in the fixtures property takes this format: plugin.$plugin_name.$model_name
3. Don’t forget to set up an empty database and include a test_suite setting in your database configuration file.

See these links for additional insight:
Cakewell Database Config File
Model Test with Fixtures
CakePhp cake_test_fixture.php

HABTM Relationships

To test models that have HABTM relationships with other models, it is necessary to create fixtures for both models having the HABTM relationship and a fixture to build the join table. See these files from the Cakewell project for examples:

Authwell User-Role HABTM Fixture
Authwell Role-Privilege HABTM Fixture

The Cakewell Authwell plugin include a good example of a complex model unit test that is successfully configured. It includes tests within the plugin directory that autoload a clean test database and successfully test models with HABTM associations. The source can be found here:

Authwell Plugin Test Directory

This post is mainly just to insure that everything is working correctly. More sporadic posting to follow.

The code is open source and available at the Cakewell Google Code site at:

http://code.google.com/p/cakewell/

The live demo can be found at:

http://cakewell.klenwell.com/

I’ll add updates here as I progress.