Re: [Django] #27227: Full text search by UUIDField returns DataError

[Django]

#27227: Full text search by UUIDField returns DataError
-+-
 Reporter:  Dan Claudiu Pop  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  UUIDField fts| Triage Stage:
  postgres   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


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

Re: [Django] #27227: Full text search by UUIDField returns DataError

[Django]

#27227: Full text search by UUIDField returns DataError
-+-
 Reporter:  danclaudiupop|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  UUIDField fts| Triage Stage:
  postgres   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 I'm not sure. Maybe you can send a pull request to give an idea of what
 the patch allows?

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

Re: [Django] #27227: Full text search by UUIDField returns DataError

[Django]

#27227: Full text search by UUIDField returns DataError
-+-
 Reporter:  danclaudiupop|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  UUIDField fts| Triage Stage:
  postgres   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by danclaudiupop):

 The use case that we encounter is this: having an administration interface
 which lists all the shows, i want to search shows by `cid`,  `title_short`
 and other fields (such as `description`, etc). So I wanted to leverage
 FTS, because `__contains` is really slow over many records and fields.

 By charettes suggestion, I used `CAST` and the queryset looks like this:
 {{{
 Show.objects.annotate(cidtxt=Cast('cid',
 TextField())).annotate(search=SearchVector('cidtxt',
 'title_short')).filter(search='foo')
 }}}

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

Re: [Django] #27227: Full text search by UUIDField returns DataError

[Django]

#27227: Full text search by UUIDField returns DataError
-+-
 Reporter:  danclaudiupop|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  UUIDField fts| Triage Stage:
  postgres   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by melvyn-sopacua):

 So unfortunately, even when supporting the fallback value, this fails
 because to_tsvector(uuid) fails for reasons pointed out by charettes: uuid
 isn't searchable. However, having a way to provide the fallback is useful,
 if one wants to have NULL returned. From the Coalesce docs:

 The COALESCE function returns the first of its arguments that is not
 null. Null is returned only if all arguments are null.

 But, I don't have a real-world use case for this. If there's no interest
 in supporting the fallback value, I'll throw away my local branch.

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

Re: [Django] #27227: Full text search by UUIDField returns DataError

[Django]

#27227: Full text search by UUIDField returns DataError
-+-
 Reporter:  danclaudiupop|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  UUIDField fts| Triage Stage:
  postgres   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by charettes):

 We could be extra safe and always cast the expression to text in a
 `CAST(expression, output_field=models.TextField())` but I don't understand
 why you're using FTS here, using `LIKE` through the `__contains` lookup
 would be more appropriate IMHO. In the meant time you can take care of
 casting the expression yourself before annotating your queryset to work
 around your issue.

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

Re: [Django] #27227: Full text search by UUIDField returns DataError

[Django]

#27227: Full text search by UUIDField returns DataError
-+-
 Reporter:  danclaudiupop|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  UUIDField fts| Triage Stage:
  postgres   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by danclaudiupop):

 We have a system in which we identify a resource by uuid field. We also
 expose a search endpoint where we give back a list of different resource
 types. For commodity we also search in the uuid field to give back the
 proper resource on the search endpoint.

 Instead of checking "/api/book//" or "/api/author//" for an
  we can go directly to "api/search/?q=" to fetch the resource.

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

Re: [Django] #27227: Full text search by UUIDField returns DataError

[Django]

#27227: Full text search by UUIDField returns DataError
-+-
 Reporter:  danclaudiupop|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  UUIDField fts| Triage Stage:
  postgres   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 What's the use case for running full text search on a UUID?

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

Re: [Django] #27227: Full text search by UUIDField returns DataError

[Django]

#27227: Full text search by UUIDField returns DataError
-+-
 Reporter:  danclaudiupop|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  UUIDField fts| Triage Stage:
  postgres   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by melvyn-sopacua):

 Analysis:

 In `django/contrib/postgres/search.py` we find  in __init__() around line
 55 (stable/1.10.x):


 {{{
 self.source_expressions = [
 Coalesce(expression, Value('')) for expression in
 self.source_expressions
 ]
 }}}

 These are propagated to Coalesce() and generate the expression:
 {{{
 COALESCE("entities_show"."cid", '')
 }}}

 For most cases, the empty string is a valid input value, yet for the
 native PostgreSQL UUID type, this is not the case. The API doesn't provide
 a way to specify the fallback value.

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

Re: [Django] #27227: Full text search by UUIDField returns DataError

[Django]

#27227: Full text search by UUIDField returns DataError
-+-
 Reporter:  danclaudiupop|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  UUIDField fts| Triage Stage:
  postgres   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by danclaudiupop):

 * cc: danclaudiupop@… (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/071.42dcf43751839d5cd04b171b5ad01c68%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27227: Full text search by UUIDField returns DataError

[Django]

#27227: Full text search by UUIDField returns DataError
-+-
 Reporter:  danclaudiupop|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.10
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  UUIDField fts| Triage Stage:
  postgres   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by danclaudiupop):

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

[Django] #27227: Full text search by UUIDField returns DataError

[Django]

#27227: Full text search by UUIDField returns DataError
--+
 Reporter:  danclaudiupop |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.10
 Severity:  Normal|   Keywords:  UUIDField fts
  |  postgres
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Consider the following model:

 {{{
 class Show(models.Model):
 cid = models.UUIDField(
 default=uuid.uuid4,
 editable=False,
 verbose_name="Content ID",
 help_text="Unique Identifier"
 )
 title_short = models.CharField(
 max_length=60,
 blank=True,
 verbose_name="Short Title",
 help_text="Short title (60 chars)"
 )
 }}}

 The following snippet returns DataError, see below traceback:

 {{{
 >>> from django.contrib.postgres.search import SearchVector
 >>> Show.objects.annotate(search=SearchVector('cid')).filter(search='foo')

 Traceback (most recent call last):
   File "", line 1, in 
   File "/home/vagrant/ve/lib/python3.4/site-
 packages/django/db/models/query.py", line 232, in __repr__
 data = list(self[:REPR_OUTPUT_SIZE + 1])
   File "/home/vagrant/ve/lib/python3.4/site-
 packages/django/db/models/query.py", line 256, in __iter__
 self._fetch_all()
   File "/home/vagrant/ve/lib/python3.4/site-
 packages/django/db/models/query.py", line 1087, in _fetch_all
 self._result_cache = list(self.iterator())
   File "/home/vagrant/ve/lib/python3.4/site-
 packages/django/db/models/query.py", line 54, in __iter__
 results = compiler.execute_sql()
   File "/home/vagrant/ve/lib/python3.4/site-
 packages/django/db/models/sql/compiler.py", line 835, in execute_sql
 cursor.execute(sql, params)
   File "/home/vagrant/ve/lib/python3.4/site-
 packages/django/db/backends/utils.py", line 79, in execute
 return super(CursorDebugWrapper, self).execute(sql, params)
   File "/home/vagrant/ve/lib/python3.4/site-
 packages/django/db/backends/utils.py", line 64, in execute
 return self.cursor.execute(sql, params)
   File "/home/vagrant/ve/lib/python3.4/site-packages/django/db/utils.py",
 line 94, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/home/vagrant/ve/lib/python3.4/site-packages/django/utils/six.py",
 line 685, in reraise
 raise value.with_traceback(tb)
   File "/home/vagrant/ve/lib/python3.4/site-
 packages/django/db/backends/utils.py", line 64, in execute
 return self.cursor.execute(sql, params)
 django.db.utils.DataError: invalid input syntax for uuid: ""
 LINE 1: ...tag", to_tsvector(COALESCE("entities_show"."cid", '')) AS "s...
 }}}

 Tried with PostgreSQL 9.3.14 and PostgreSQL 9.5.3

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