Re: [Django] #29171: PostgreSQL specific model fields - ArrayField: Type Mismatch

2018-03-11 Thread Django
#29171: PostgreSQL specific model fields - ArrayField: Type Mismatch
-+-
 Reporter:  Pal  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  Postgres Array   | Triage Stage:
  Query  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Pal):

 * status:  new => closed
 * resolution:   => worksforme


-- 
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/063.01d4d004dc7296a22a8dd02f51e6d2a3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #29171: PostgreSQL specific model fields - ArrayField: Type Mismatch

2018-03-05 Thread Django
#29171: PostgreSQL specific model fields - ArrayField: Type Mismatch
-+-
 Reporter:  Pal  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Postgres Array   | Triage Stage:
  Query  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 I'm still not sure we have enough details to reproduce the issue. What
 does the SQL for the table look like, what does your model look like, and
 what does the failing QuerySet look like?

-- 
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/063.b020ff2a9ae684664b6e22c5a15a9744%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #29171: PostgreSQL specific model fields - ArrayField: Type Mismatch

2018-03-04 Thread Django
#29171: PostgreSQL specific model fields - ArrayField: Type Mismatch
-+-
 Reporter:  Pal  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Postgres Array   | Triage Stage:
  Query  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Pal):

 Replying to [comment:5 Tim Graham]:
 > Please show the model and the query. Perhaps you could write it as a
 test for `tests/postgres_tests/test_array.py` using `CharArrayModel`.
 One thing I want to mention is that this table was already created in
 Postgres and I am adding that to the models.py and as I said if I define
 as ArrayField(models.CharField...) it does not work where as
 ArrayField(models.TextField...) works. So someone can test and verify
 this. Thanks.

-- 
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/063.ce6706dbb60df62c41bcc29a06656724%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #29171: PostgreSQL specific model fields - ArrayField: Type Mismatch

2018-03-01 Thread Django
#29171: PostgreSQL specific model fields - ArrayField: Type Mismatch
-+-
 Reporter:  Pal  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Postgres Array   | Triage Stage:
  Query  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 Please show the model and the query. Perhaps you could write it as a test
 for `tests/postgres_tests/test_array.py` using `CharArrayModel`.

-- 
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/063.d025c8204809d9bb1582b3c1fda5d6d1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #29171: PostgreSQL specific model fields - ArrayField: Type Mismatch

2018-03-01 Thread Django
#29171: PostgreSQL specific model fields - ArrayField: Type Mismatch
-+-
 Reporter:  Pal  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Postgres Array   | Triage Stage:
  Query  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * cc: felixxm (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 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/063.d2ce02d67a1ba745f4b3decb8bd87a40%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #29171: PostgreSQL specific model fields - ArrayField: Type Mismatch

2018-03-01 Thread Django
#29171: PostgreSQL specific model fields - ArrayField: Type Mismatch
-+-
 Reporter:  Pal  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Postgres Array   | Triage Stage:
  Query  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Pal):

 Replying to [comment:2 Simon Charette]:
 > Could you provide a traceback and more details about how ''it fails''?
 >
 > Does it happen when you define a model using `ArrayField(CharField())`,
 when performing a query annotation?

 Yes. When I defined the model as shown in the documentation at
 https://docs.djangoproject.com/en/2.0/ref/contrib/postgres/fields
 /#querying-arrayfield , the query fails. But if I change models.CharField
 to models.TextField, the query succeeds.

 Here are the error statements from apache2 error log:
 psycopg2.ProgrammingError: operator does not exist: text[] @> character
 varying[]
 django.db.utils.ProgrammingError: operator does not exist: text[] @>
 character varying[]

 May be we need to change the documentation to reflect the change above.
 Thanks.

-- 
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/063.3c6c267e692c16e2d0f8c5990ce597bb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #29171: PostgreSQL specific model fields - ArrayField: Type Mismatch

2018-02-28 Thread Django
#29171: PostgreSQL specific model fields - ArrayField: Type Mismatch
-+-
 Reporter:  Pal  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Postgres Array   | Triage Stage:
  Query  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Could you provide a traceback and more details about how ''it fails''?

 Does it happen when you define a model using `ArrayField(CharField())`,
 when performing a query annotation?

-- 
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/063.1a2d9539060e6faca0f8b2cf94e2721b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #29171: PostgreSQL specific model fields - ArrayField: Type Mismatch

2018-02-28 Thread Django
#29171: PostgreSQL specific model fields - ArrayField: Type Mismatch
-+-
 Reporter:  Pal  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Postgres Array   | Triage Stage:
  Query  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Pal):

 * type:  Uncategorized => Bug


-- 
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/063.ada286db57595ebc220a5a54bb5fb80f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


[Django] #29171: PostgreSQL specific model fields - ArrayField: Type Mismatch

2018-02-28 Thread Django
#29171: PostgreSQL specific model fields - ArrayField: Type Mismatch
-+-
   Reporter:  Pal|  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component:  Database   |Version:  2.0
  layer (models, ORM)|   Keywords:  Postgres Array
   Severity:  Normal |  Query
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 When you define ArrayField as models.CharField, the query fails. But if
 you define ArrayField as models.TextField, the query succeeds.

 Not Working: ArrayField(models.CharField(max_length=200), blank=True)

 Working: ArrayField(models.TextField(blank=True))

-- 
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/048.e717297e2d31584d6b2ef469a84842a3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.