Fixing DC-755 with tests

Corrects handling of MODEL_CLASS_PREFIX when migrating from YAML schema files so that the prefix is used for from and to models to correct behaviour where the whole database is dropped, and adding ticket tests
Adding tests for DC880 spurious migrations added when using behaviours
DC880 - Adding explicit tableName definition to versionable and searchable to prevent false migration generation

When using model prefixes and the searchable and versionable behaviours, migrations are built that drop and recreate indexes when nothing of the schema has changed. This commit fixes this by explicitly declaring a table name in these behaviours (based on the tablename of the owning class) so that the tablename for generated models is correct. Child classes can still override this value in their extended classes if required.
Case sensistivity issues with table name
composer.json renamed into rezzza/doctrine1
Fixes E_NOTICE when using array_diff with PHP 5.4 fixes #50
Revert "Fixes E_NOTICE when using array_diff with PHP 5.4"

This reverts commit c28c6e8e461c5b4198cc029622386750da9121ff.
Merge remote-tracking branch 'rezzo/1.2.5' into array-diff

Conflicts:
	composer.json
Merge pull request #4 from SlikNL/master

Fix precedence problem with pending join conditions
Merge pull request #5 from SlikNL/array-diff

PHP 5.4 array_diff() compatibility
Portability files for Derby, Splice and JdbcBridge
Merge pull request #7 from rgasch/portability

Portability files for Derby, Splice and JdbcBridge
Improvements to Jdbcbridge Adapter
Merge pull request #8 from rgasch/portability

Improvements to Jdbcbridge Adapter
Added support for DB schemas
Merge pull request #9 from rgasch/portability

Added support for DB schemas
Updating slug in I18N behaviour yields non-unique slug

This simple patch fixes DC-728, implementing Christian Seaman solution, see http://www.doctrine-project.org/jira/browse/DC-728
Merge pull request #10 from endelwar/master

Updating slug in I18N behaviour yields non-unique slug
Increasing Geographical behaviour precision to 8 decimal

When using the Geographical behaviour in a YML schema the latitude is stored in Mysql as a Double(18,2) instead of a Double as it was in previous versions.
With only 2 decimal places, the accuracy of the geographic point drops to about 1 km (see [Wikipedia page about Decimal Degrees](http://en.wikipedia.org/wiki/Decimal_degrees) )
This patch fixes [DC-648](http://www.doctrine-project.org/jira/browse/DC-648)
Merge pull request #11 from endelwar/master

Increasing Geographical behaviour precision to 8 decimal