Re: [Django] #22673: inspectdb not support database schema on postgresql with name different of "public"

[Django]

#22673: inspectdb not support database schema on postgresql with name different 
of
"public"
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  inspectdb,   | Triage Stage:  Accepted
  introspection, postgresql, schema  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018e3151d374-39e19726-d683-4cad-8d3d-4bcd645cb4b9-00%40eu-central-1.amazonses.com.

Re: [Django] #22673: inspectdb not support database schema on postgresql with name different of "public"

[Django]

#22673: inspectdb not support database schema on postgresql with name different 
of
"public"
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  inspectdb,   | Triage Stage:  Accepted
  introspection, postgresql, schema  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Erik Cederstrand):

 I just stumbled into this because I have similar requirements, and ended
 up creating a custom
 `django.db.backends.postgresql.introspection.DatabaseIntrospection` class
 that respects the schema specified by `inspectdb --database=my_schema`. I
 also implemented a new optional `SCHEMA` entry in the postgres
 `settings.DATABASES` option dict so the inspection can pick up that value.

 The changes to the `DatabaseIntrospection` and `DatabaseWrapper` classes
 are minimal. Fallback would be to the point to the `public` schema.

 Would you be interested in patches?

 It's a bit more involved to support multiple schemas in parallel, but
 solveable by creating a custom DB router and an extra `db_schema` Meta
 option.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/109.066db0932454a606787840290861d2a6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22673: inspectdb not support database schema on postgresql with name different of "public"

[Django]

#22673: inspectdb not support database schema on postgresql with name different 
of
"public"
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  inspectdb,   | Triage Stage:  Accepted
  introspection, postgresql, schema  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson):

 Related report #29494

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/109.abf6b4bd2926b6faf528e8414a06a0d0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22673: inspectdb not support database schema on postgresql with name different of "public"

[Django]

#22673: inspectdb not support database schema on postgresql with name different 
of
"public"
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  inspectdb,   | Triage Stage:  Accepted
  introspection, postgresql, schema  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Jaap Vermeulen):

 With a simple code change, schemas in postgres work fine (but not for
 inspectdb).  I will paste the change here and if I find time later on will
 create a pull request and also add the second change in there (from
 #27908) for inspectdb.  In db/backends/postgresql/operations.py replace
 the following method:
 {{{
 def quote_name(self, name):
 if name.startswith('"') and name.endswith('"'):
 return name  # Quoting once is enough.
 # Quote schema and db seperately
 parts = name.split('.')
 return '"' + '"."'.join(parts) + '"'

 }}}
 If and when I have time, I'll see if I can look at the other DBs.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/109.0a3a221a6819ce5ca9ea77ca3cb59f25%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22673: inspectdb not support database schema on postgresql with name different of "public"

[Django]

#22673: inspectdb not support database schema on postgresql with name different 
of
"public"
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  inspectdb,   | Triage Stage:  Accepted
  introspection, postgresql, schema  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by shaib):

 * keywords:  inspectdb, introspection, postgresql, schema, oracle =>
 inspectdb, introspection, postgresql, schema


Comment:

 (No response to my question of a year ago, oracle keyword removed)

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/109.cb6d17c5e6674abe4be854b88121dc35%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22673: inspectdb not support database schema on postgresql with name different of "public"

[Django]

#22673: inspectdb not support database schema on postgresql with name different 
of
"public"
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  inspectdb,   | Triage Stage:  Accepted
  introspection, postgresql, |
  schema, oracle |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by luzfcb):

 Is there anybody working on something that makes this possible in a future
 version of django(1.8, 1.9, 2.0)?

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/109.4490d592d8c766461e542eff12da3aa7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22673: inspectdb not support database schema on postgresql with name different of "public"

[Django]

#22673: inspectdb not support database schema on postgresql with name different 
of
"public"
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  inspectdb,   |  Patch needs improvement:  0
  introspection, postgresql, |UI/UX:  0
  schema, oracle |
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by shai):

 Oracle doesn't have schemas in the sense of PG; @luzfcb -- are you sure
 Oracle is related here?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/109.4b7e6d218e1d99ad382db557390c8f44%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22673: inspectdb not support database schema on postgresql with name different of "public"

[Django]

#22673: inspectdb not support database schema on postgresql with name different 
of
"public"
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  inspectdb,   |  Patch needs improvement:  0
  introspection, postgresql, |UI/UX:  0
  schema, oracle |
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * component:  Uncategorized => Database layer (models, ORM)
 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/109.c923f229fe867c4f6c9d1e0b15113304%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22673: inspectdb not support database schema on postgresql with name different of "public"

[Django]

#22673: inspectdb not support database schema on postgresql with name different 
of
"public"
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  inspectdb,   |  Unreviewed
  introspection, postgresql, |  Needs documentation:  0
  schema, oracle |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by luzfcb):

 * keywords:  inspectdb, introspection, postgresql, schema => inspectdb,
 introspection, postgresql, schema, oracle


Comment:

 Replying to [comment:3 andrewgodwin]:

 Thanks for the quick reply.

 Due to this being a very old request (#1051 #6148 ), I believe that the
 indicated provisory solution should be described step by step in the
 documentation, including citing that it is a provisory solution and are
 still searching for a permanent solution, indicating their respective
 tickets.

 At the moment I do not possess necessary knowledge to solve this, but I
 think explicit the problems to django-community is good, because at some
 point someone will arrive at a good solution for this.

 I really like the pep 20
 "Explicit is better than implicit."

 This feature would be especially useful for me because I need to integrate
 the system that I am developing with django with other systems already in
 operation at least 10 years, and made ​with ASP.net, Java and C++, using
 Oracle and PostgreSQL schema with name different of "public".

 Thanks for the hard work

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/109.0bfcf134577fb1c38756598d149cee9f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22673: inspectdb not support database schema on postgresql with name different of "public"

[Django]

#22673: inspectdb not support database schema on postgresql with name different 
of
"public"
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  inspectdb,   |  Unreviewed
  introspection, postgresql, schema  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by andrewgodwin):

 As per #6148, Django doesn't actually support schemas, so I'm not sure we
 can resolve this until that's fixed.

 Schema support is a big task for us and hopefully one we can support soon,
 but it's not a quick thing to implement! The only workaround I could think
 of would be using set_search_path in initial connection SQL (some comments
 on that in the ticket above or google around for how other people have
 done it) to make sure the other schema is included and then inspectdb
 might see the tables in it.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/109.8537e080919406e81a8f2db2c7ac4e77%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22673: inspectdb not support database schema on postgresql with name different of "public"

[Django]

#22673: inspectdb not support database schema on postgresql with name different 
of
"public"
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  inspectdb,   |  Unreviewed
  introspection, postgresql, schema  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by luzfcb):

 * version:  1.6 => master


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/109.4e4347a13e985e388448f2dae30740ff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22673: inspectdb not support database schema on postgresql with name different of "public"

[Django]

#22673: inspectdb not support database schema on postgresql with name different 
of
"public"
-+-
 Reporter:  Fabio Caritas|Owner:  nobody
  Barrionuevo da Luz   |   Status:  new
 Type:  New feature  |  Version:  1.6
Component:  Uncategorized|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  inspectdb,   |  Unreviewed
  introspection, postgresql, schema  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Fabio Caritas Barrionuevo da Luz ):

 * cc: bnafta@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/109.d551c94c92cbb2f9315019e898d24467%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22673: inspectdb not support database schema on postgresql with name different of "public"

[Django]

#22673: inspectdb not support database schema on postgresql with name different 
of
"public"
-+-
 Reporter:  Fabio Caritas|  Owner:  nobody
  Barrionuevo da Luz   | Status:  new
 Type:  New feature  |Version:  1.6
Component:  Uncategorized|   Keywords:  inspectdb,
 Severity:  Normal   |  introspection, postgresql, schema
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 I have a legacy database in PostgreSQL, which is still in production.
 I want to migrate it to Django.
 I tried to do the reverse engineering of the database using inspectdb to
 generate models classes, however, this does not work.

 '''The problem is Django not provides way to use inspectdb in a schema
 with name different of "public"'''

 If you do not know the concept of postgresql schema, please read:

 http://www.postgresql.org/docs/9.3/static/ddl-schemas.html

 To explain this, I created a database based on "pulls" app from the basic
 tutorial.

 The backup of database I used is attached.


 * It would facilitate integration with legacy database

 I found these tickets dealing with similar things but different this

 https://code.djangoproject.com/ticket/1051
 https://code.djangoproject.com/ticket/6148


 I set my settings like this:

 {{{#!python


 DATABASES = {
 # new blank database
 # this read/write into "public" postgresql schema
 'default': {
 'ENGINE': 'django.db.backends.postgresql_psycopg2',
 'NAME': 'neweposse',
 'USER': 'postgres',
 'PASSWORD': 'postgres',
 'HOST': '127.0.0.1',
 'PORT': '5432',
 },
 # legacy database
 # the postgresql schema is named "legacyschema1"
 'eposse': {
 'ENGINE': 'django.db.backends.postgresql_psycopg2',
 'NAME': 'eposse',
 'USER': 'postgres',
 'PASSWORD': 'postgres',
 'HOST': '127.0.0.1',
 'PORT': '5432',
 }
 }

 }}}

 '''in terminal:'''

 {{{#!bash

 (django1.7b4)oficina@oficina:~/schematest$ python manage.py inspectdb
 ...
 from __future__ import unicode_literals

 from django.db import models

 (django1.7b4)oficina@oficina:~/schematest$ python manage.py inspectdb
 --database=eposse
 ...
 from __future__ import unicode_literals

 from django.db import models

 }}}

 '''Tests using dbshell, was recommended to me by Russell Keith-Magee this
 topic: https://groups.google.com/forum/#!topic/django-
 developers/lSHrDFZM4lQ'''

 {{{#!bash

 (django1.7b4)oficina@oficina:~/schematest$ python manage.py dbshell
 --database=eposse
 psql (9.3.4)
 SSL connection (cipher: DHE-RSA-AES256-SHA, bits: 256)
 Type "help" for help.

 eposse=# \dt
 No relations found.

 }}}

 {{{#!bash

 eposse=# \dn
  List of schemas
  Name  |  Owner
 ---+--
  legacyschema1 | postgres
  public| postgres
 (2 rows)

 }}}

 {{{#!bash

 eposse=# \dt legacyschema1.*
  List of relations
 Schema |  Name  | Type  |  Owner
 ---++---+--
  legacyschema1 | choice | table | postgres
  legacyschema1 | pull   | table | postgres
 (2 rows)

 }}}

 {{{#!bash

 eposse=# \d legacyschema1.*
Table "legacyschema1.choice"
Column|  Type  |
 Modifiers
 
-++---
  id  | integer| not null default
 nextval('legacyschema1.choice_id_seq'::regclass)
  poll_id | integer| not null
  choice_text | character varying(200) | not null
  votes   | integer| not null
 Indexes:
 "choice_pkey" PRIMARY KEY, btree (id)
 "choice_582e9e5a" btree (poll_id)
 Foreign-key constraints:
 "choice_poll_id_3d0280c389b7efa_fk_pull_id" FOREIGN KEY (poll_id)
 REFERENCES legacyschema1.pull(id) DEFERRABLE INITIALLY DEFERRED

 Index "legacyschema1.choice_582e9e5a"
  Column  |  Type   | Definition
 -+-+
  poll_id | integer | poll_id
 btree, for table "legacyschema1.choice"

 Sequence "legacyschema1.choice_id_seq"
 Column |  Type   |Value
 ---+-+-
  sequence_name | name| choice_id_seq
  last_value| bigint  | 2
  start_value   | bigint  | 1
  increment_by  | bigint  | 1
  max_value | bigint  | 9223372036854775807
  min_value | bigint  | 1
  cache_value   | bigint  | 1
  log_cnt   | bigint  | 0
  is_cycled | boolean | f
  is_called | boolean | t
 Owned by: legacyschema1.choice.id

 Index "legacyschema1.choice_pkey"
  Column |  Type   | Definition
 +-+
  id | integer | id
 primary key, btree, for table