If you know Javascript, then this isn’t a suprise:

typeof {a: 4}; //"object"
typeof [1, 2, 3]; //"object"
(function() {console.log(typeof arguments)})(); //object
typeof new ReferenceError; //"object"
typeof new Date; //"object"
typeof /a-z/; //"object"
typeof Math; //"object"
typeof JSON; //"object"
typeof new Number(4); //"object"
typeof new String("abc"); //"object"
typeof new Boolean(true); //"object"

But thanks to some dilligent work by one Angus Croll, you can do something like:

toType({a: 4}); //"object"
toType([1, 2, 3]); //"array"
(function() {console.log(toType(arguments))})(); //arguments
toType(new ReferenceError); //"error"
toType(new Date); //"date"
toType(/a-z/); //"regexp"
toType(Math); //"math"
toType(JSON); //"json"
toType(new Number(4)); //"number"
toType(new String("abc")); //"string"
toType(new Boolean(true)); //"boolean"

Check out the full explanation @
http://javascriptweblog.wordpress.com/2011/08/08/fixing-the-javascript-typeof-operator/

https://github.com/devdave/PyProxy

ProxyProject

• Author: David W
• Status: Pre-Alpha

Primary goal

ProxyProject is initially meant to resolve one very common and VERY tedious part of Web development,
validating web forms. A developer would place Proxy Project between their browser and their development environment
then run through the process of populating and submitting a form. After the developer would return to the Proxy
Project control panel and click a button, in return a python mechanize script would be presented.

Secondary goals

Since the Proxy is already recording everything, additional features would be the ability to replay the response side
of requestes on demand ( basically caching the respons ).

The ability to mechanize scripts into “story” scripts, to make it easier to re-use and organize them for building up
front loaded system under-test scripts.

Could be nice goals

A tool to marry SQL statements stored in a MySQL general log file to individual responses, perhaps make it easier to add
additional DB level post mechanize

Use case: You have a search form with multiple search criteria “name”, “id”, “type”, etc.

In your entity’s repository you would have a function like

Note, trying to use Gist for inline code, if it doesn’t work/render then go here https://gist.github.com/1039231

It’s important to note the setParameter call is responsible for wrapping the value in %’s and NOT the where expression itself. At the PDO driver layer, it either ignores or is aware of wrapped % symbology and allows those characters to get past the input scrubbers.

Minus the ->select expression, this could conceivably be portable to any and all Entities by shoving an application level EntityRepostory class between the individual entities and the Doctrine EntityRepository.

Keep end up going back to this answer repeatedly as I keep forgetting to snapshot a clean slate PHP5 dev. VM.

http://superuser.com/questions/55055/how-to-install-an-updated-version-of-pear-phpunit-on-ubuntu/55072#55072

I’ve been looking at upgrading one of my past clients from Doctrine 1 to Doctrine 2 and so far it’s looking from my end like a done deal.

I started here by paging through this ( http://www.slideshare.net/jwage/doctrine-2-not-the-same-old-php-orm ) slideshare on Doctrine 2 and before I got bored with paging through 94 slides I already had a warm fuzzy feeling.

My initial tests have shown that Doctrine 2 without a doubt needs support from APC or memcached, but with the exception my few and far between dumb/cheap client’s is almost guaranteed to be present. Otherwise I like the decidedly simpler syntax for defining domain models as simple classes without inheriting some super support class.

Last bit, my stackoverflow answers regarding doctrine 2 so far
http://stackoverflow.com/questions/5954618/does-doctrine-2-0-pre-generate-model-classes-like-propel-1-5-does/5955400#5955400