-
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
manage.py inspectdb: All redshift tables fail with unable to inspect table - function unnest(int2vector) does not exist #13
Comments
Same issue here |
same problem |
1 similar comment
same problem |
Any update on this issue? |
I'm getting:
I'm using django-redshift-backend version 0.9.1 Please, any news on this issue? |
Django currently supports PostgreSQL >= 9.4 and Redshift's API are 8.x based. Related info
Notes
|
Is there any workaround for this issue? |
Based on detailed information from @Surgo (thanx!) I used a workaround by using older django version to do the inspection. I have A LOT of tables (and am lazy) so here it is: mkdir tmp && cd tmp
virtualenv -p python2 venv
source venv/bin/activate
pip install django==1.4.0 psycopg2
django-admin.py startproject djangold
cd djangold
export PYTHONPATH=$(pwd)
export DJANGO_SETTINGS_MODULE=djangold.settings
# Update your settings to include
# DATABASES = {
# 'default': {
# 'ENGINE': 'django.db.backends.postgresql_psycopg2',
# 'NAME': 'db_name',
# 'USER': 'username',
# 'PASSWORD': 'pwd',
# 'HOST': 'host',
# 'PORT': '5439',
# 'OPTIONS': {
# 'options': '-c search_path=schema_name', # if using schema
# }
# },
#}
# Voila! Now it works
django-admin.py inspectdb I hope this helps: @epineda @gauravnexus |
Thanks for the above solution! For anyone getting:
I was able to get around this by going all the way back to Django 1.2 |
Unable to inspect table 'auth_group' - Can anyone help with this mistake? Django... |
@RicoChivela1, this message typically indicates that the table is missing. Did you run |
I am getting
on
|
Same issue here...Based on @hlodver 's solution (thx!) and I tested that the last working version of django is 1.7.11 which is slightly better than django==1.4 for me, in the way that 1.7.11 added one extra line
just for anyone who needs this... |
fixed by #90 . Thanks to @MattFisher ! |
It has been released https://pypi.org/project/django-redshift-backend/3.0.0/ |
I have:
and:
I am running the following command:
And I get the following output on every table in my redshift schema:
It seems like the driver is falling back to postgres 9.x despite my database settings:
The text was updated successfully, but these errors were encountered: