-
Notifications
You must be signed in to change notification settings - Fork 65
Support for PostGIS backend optionally #12
base: master
Are you sure you want to change the base?
Conversation
Wouldn't it be better to implement a setting where you specify your BaseDatabaseWrapper, DjangoCursorWrapper and BaseDatabaseCreation of choice? Then this would work with django-hstore and more, as well. |
+1, Mozilla's MySQL pool works this way. I would love to implement that. |
So I wanted to do that originally, but I found if I tried to import any DatabaseWrappers inside the Django settings file, I run into this error:
|
You could just write a string in the settings file and then do the import in the module, based in the settings value ;) e.g. DATABASE_POOL_CONFIG = {
'BaseDatabaseWrapper': 'some.path.to.BaseDatabaseWrapper',
'DjangoCursorWrapper': 'some.path.to.DjangoCursorWrapper',
'BaseDatabaseCreation': 'some.path.to.BaseDatabaseCreation'
} |
I tried something like this:
but I end up with errors because you refer to many components of django.contrib.gis.db.backends.postgis.base by importing *..
|
I have actually a big + one for this ! |
Was the support for django.contrib.gis.db.backends.postgis added elsewhere? |
also interested in where this landed....is there a way to use postgis with this library? |
+1 for being able to use PostGIS with Django-PostgresPool |
Still no support/planned support for postgis in postgrespool? |
Optionally support django.contrib.gis.db.backends.postgis as the DB backend