Added basic support for a postgresql driver

* Base model templates have been updated to escape quotes in the relation queries, since PG uses a double quote for denoting object names (rather than the MySQL back tick)
* Columns that are `auto_increment` or `sequence` are noted as being `serial`. When inserting a new row the column value is set to `DEFAULT` (unless it has been overridden post-`__construct`)
* A few sundry utility methods
* Removed the `LIMIT` on `UPDATE` statements since PG doesn't support this. Not sure if this has any further ramifications.
* Detection when adding duplicate columns/relations to tables in the generator.

Overall, there is an inconsistent use `schema` and `database`, since MySQL's language is not strictly the same as PostgreSQL. This could be addressed by moving to the more formal language used by PostgreSQL, and adapting the MySQL driver to fill in the blanks. Not sure if this makes sense or not, need further discussion about the intricacies of language between the two.
Tweaks for MySQL driver to support DEFAULT values

The driver will now set the correct default values since MySQL 5.6 doesn't seem to like coercing `''` into integer values anymore, which broke the inserting of rows where foreign keys were nullable.

If a column is nullable then it's default value will always be null.
Added basic support for a postgresql driver

* Base model templates have been updated to escape quotes in the relation queries, since PG uses a double quote for denoting object names (rather than the MySQL back tick)
* Columns that are `auto_increment` or `sequence` are noted as being `serial`. When inserting a new row the column value is set to `DEFAULT` (unless it has been overridden post-`__construct`)
* A few sundry utility methods
* Removed the `LIMIT` on `UPDATE` statements since PG doesn't support this. Not sure if this has any further ramifications.
* Detection when adding duplicate columns/relations to tables in the generator.

Overall, there is an inconsistent use `schema` and `database`, since MySQL's language is not strictly the same as PostgreSQL. This could be addressed by moving to the more formal language used by PostgreSQL, and adapting the MySQL driver to fill in the blanks. Not sure if this makes sense or not, need further discussion about the intricacies of language between the two.
Tweaks for MySQL driver to support DEFAULT values

The driver will now set the correct default values since MySQL 5.6 doesn't seem to like coercing `''` into integer values anymore, which broke the inserting of rows where foreign keys were nullable.

If a column is nullable then it's default value will always be null.
Merge branch 'postgresql-driver' of git://github.com/wave-framework/wave into postgresql-driver
Fixed bad column name
Merge pull request #10 from wave-framework/master

Sync with master for bugfixes
Add bigint type recognition
Fixed namespace expansion where a model shares the same name as its namespace.
Merge pull request #9 from wave-framework/postgresql-driver

Added basic support for a postgresql driver