Prevents stack level too deep on inverse_of relations

When a relation is specified with an inverse_of the association_cache
will loop continuously between the parent and child records causing a
stack level too deep, this fix prevents this by checking for the
presence of the record in the output_hash first, added inverse of to
test models as well to test for this condition.
Merge pull request #19 from warmlyyours/master

Prevents stack level too deep on inverse_of relations
Support for foreign key and postgresql

When using database foreign keys the order of insertion is important.
On PostgreSQL however it is possible to defer the execution of these
checks until the end of the transaction block.  This provides wraps all
insert into a transaction, executes the SET CONSTRAINTS ALL DEFERRED on
initialization of extractor and also append cascade to all database
truncate call.
Support for foreign key and postgresql

When using database foreign keys the order of insertion is important.
On PostgreSQL however it is possible to defer the execution of these
checks until the end of the transaction block.  This provides wraps all
insert into a transaction, executes the SET CONSTRAINTS ALL DEFERRED on
initialization of extractor and also append cascade to all database
truncate call.
Merge branch 'master' of github.com:warmlyyours/iron_fixture_extractor
Merge pull request #20 from warmlyyours/master

Support for foreign key and postgresql, wraps all inserts into a transaction with a deferred constraint check execution.