CursorWrapper eroneously sending connection_created signal a second time...

... (and sends itself, instead of a Connection Object).  This can cause handlers listening to that signal to fail.

our database wrapper inherits from django.db.backends.BaseDatabaseWrapper which already sends this signal (correctly) from its BaseDatabaseWrapper.connect method.

Sending it a second time from within our CusrsorWrapper seems to be needless, and again, can cause other signal handlers to fail b/c that signal is expecting a DatabaseWrapper to be passed, not a CursorWrapper.

This behavior actually changed in Django 1.6 which causes the issue.