Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
-+-
 Reporter:  Mark Anderson|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle TextField | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Shai Berger):

 Two points:

 Replying to [comment:16 Mariusz Felisiak]:
 > Replying to [comment:15 Mariusz Felisiak]:
 > > [https://github.com/django/django/pull/15100 PR]

 IIUC, the PR discussion seems to include a workaround (a setting that
 makes the error go away). It may be worthwhile to include it in
 [https://docs.djangoproject.com/en/3.2/ref/databases/#id14 the oracle
 notes].

 > CI confirmed that it's still an issue.

 My old [https://github.com/django/django/pull/3544 PR] includes a
 technical solution to the problem. It was put on hold all these years ago,
 because I tried to do something additional in it: Define a general way for
 database backends to override a built-in lookup, without blatant
 monkeypatching. With that, the Oracle solution was done in a way which
 would have been available to a 3rd-party database backend.

 It may or may not be worthwhile to revive that idea, but either way, we
 can also take the technical Oracle solution that's given there, and apply
 it "the old way"; I hope it still works.

-- 
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/070.a5b758aaf71d402585771870a4fc%40djangoproject.com.

Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
-+-
 Reporter:  Mark Anderson|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle TextField | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 Replying to [comment:15 Mariusz Felisiak]:
 > I couldn't reproduce a crash on Oracle 12c+ and Django 2.0+.
 Unfortunately, I'm not sure where (Django/Oracle/cx_Oracle) and when it
 was fixed, [https://github.com/django/django/pull/15100 PR]

 CI confirmed that it's still an 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.21727f445ce553f8f5eb56e729c2226e%40djangoproject.com.

Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
-+-
 Reporter:  Mark Anderson|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle TextField | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  Shai Berger => (none)
 * status:  assigned => new


Comment:

 I couldn't reproduce a crash on Oracle 12c+ and Django 2.0+.
 Unfortunately, I'm not sure where (Django/Oracle/cx_Oracle) and when it
 was fixed, [https://github.com/django/django/pull/15100 PR]

-- 
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/070.de9aefa2523537722e02729065042643%40djangoproject.com.

Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
-+-
 Reporter:  Mark Anderson|Owner:  Shai
 |  Berger
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle TextField | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Mariusz Felisiak:

Old description:

> I have tried __icontains and __regex against a TextField on an oracle
> database and get the following error:
>
> DatabaseError: ORA-06502: PL/SQL: numeric or value error: character
> string buffer too small
> ORA-06512: at line 1
>
> The code was ported directly over from mysql where the i_contains query
> worked. The column was created as an NCLOB.  I can query against other
> fields fine.
>
> Environment:
>
> Request Method: GET
> Request URL: http://django/eis/banobj/search/?q=class
> Django Version: 1.1 rc 1 SVN-11348
> Python Version: 2.4.3
> Installed Applications:
> ['django.contrib.auth',
>  'django.contrib.contenttypes',
>  'django.contrib.sessions',
>  'django.contrib.sites',
>  'eis.banobj',
>  'django.contrib.admin',
>  'django.contrib.admindocs',
>  'eis.ldapauth',
>  'eis.emailLogs']
> Installed Middleware:
> ('django.middleware.common.CommonMiddleware',
>  'django.contrib.sessions.middleware.SessionMiddleware',
>  'django.contrib.auth.middleware.AuthenticationMiddleware')
>

> Template error:
> In template /opt/django/eis/templates/banobj/arealist.html, error at line
> 17
>Caught an exception while rendering: ORA-06502: PL/SQL: numeric or
> value error: character string buffer too small
> ORA-06512: at line 1
>
>7 : {% block content %}
>

>8 :  {{heading}} 
>

>9 : 
>

>10 : 
>

>11 :Banner Object
>

>12 :Ready For Testing
>

>13 :Tested
>

>14 :Primary User
>

>15 :Object Type
>

>16 : 
>

>17 :  {% for obj in  obj_list %}
>

>18 : 
>

>19 :{{ obj.name|upper
> }}
>

>20 :{% if obj.prod_svn %}
>

>21 :   
>

>22 :{% else %}
>

>23 :
>

>24 :{% endif %}
>

>25 :{% if obj.user_tested %}
>

>26 :   
>

>27 :{% else %}
>

> Traceback:
> File "/usr/lib/python2.4/site-packages/django/core/handlers/base.py" in
> get_response
>   92. response = callback(request, *callback_args,
> **callback_kwargs)
> File "/usr/lib/python2.4/site-packages/django/contrib/auth/decorators.py"
> in __call__
>   78. return self.view_func(request, *args, **kwargs)
> File "/opt/django/eis/banobj/views.py" in search
>   172.
> context_instance=RequestContext(request))
> File "/usr/lib/python2.4/site-packages/django/shortcuts/__init__.py" in
> render_to_response
>   20. return HttpResponse(loader.render_to_string(*args, **kwargs),
> **httpresponse_kwargs)
> File "/usr/lib/python2.4/site-packages/django/template/loader.py" in
> render_to_string
>   108. return t.render(context_instance)
> File "/usr/lib/python2.4/site-packages/django/template/__init__.py" in
> render
>   178. return self.nodelist.render(context)
> File "/usr/lib/python2.4/site-packages/django/template/__init__.py" in
> render
>   779. bits.append(self.render_node(node, context))
> File "/usr/lib/python2.4/site-packages/django/template/debug.py" in
> render_node
>   71. result = node.render(context)
> File "/usr/lib/python2.4/site-packages/django/template/loader_tags.py" in
> render
>   97. return compiled_parent.render(context)
> File "/usr/lib/python2.4/site-packages/django/template/__init__.py" in
> render
>   178. return self.nodelist.render(context)
> File "/usr/lib/python2.4/site-packages/django/template/__init__.py" in
> render
>   779. bits.append(self.render_node(node, context))
> File "/usr/lib/python2.4/site-packages/django/template/debug.py" in
> render_node
>   71. result = node.render(context)
> File "/usr/lib/python2.4/site-packages/django/template/loader_tags.py" in
> render
>   24. result = self.nodelist.render(context)
> File "/usr/lib/python2.4/site-packages/django/template/__init__.py" in
> render
>   779. bits.append(self.render_node(node, context))
> File "/usr/lib/python2.4/site-packages/django/template/debug.py" in
> render_node
>   81. raise wrapped
>
> Exception Type: TemplateSyntaxError at /banobj/search/
> Exceptio

Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
-+-
 Reporter:  Mark Anderson|Owner:  Shai
 |  Berger
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle TextField | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.28e520db50ae50e0b082f0ef56e387de%40djangoproject.com.

Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
-+-
 Reporter:  nosrednakram |Owner:  shaib
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle TextField |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by shaib):

 Partial [https://github.com/django/django/pull/3544 PR] fixes the
 `contains` lookup, up for review of the method of installing backend-
 specific custom lookups.

 Note that the code uses DBMS_LOB.INSTR -- the preferable way to do this is
 using CONTAINS, but that requires the text-field to be indexed.

 Just removing the DBMS_LOB.SUBSTR as suggested works with the LIKE
 queries, but breaks the exact ones.

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

Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
-+-
 Reporter:  nosrednakram |Owner:  shaib
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle TextField |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by shaib):

 * owner:  nobody => shaib
 * status:  new => assigned


Comment:

 Well, I can reproduce this on master... needs fixing.

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

Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
-+-
 Reporter:  nosrednakram |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle TextField |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by susundberg):

 Hey all, i had the same problem. I am using django-1.4 (for customer
 reason) and "Oracle Database 11g Release 11.2.0.4.0 - 64bit Production".

 Using the PyKAB patch (remove DBMS_LOB.SUBSTR ) did remove the problem
 with count() call, but it introduces new bug that causes that query ..
 exclude( my_textfield = "" ) not work properly: also the ones that have ""
 content are returned.

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

Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
-+-
 Reporter:  nosrednakram |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle TextField |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by PyKaB):

 * version:  1.1-beta => 1.6


Comment:

 It's no need to use function DBMS_LOB.SUBSTR in oracle 11g or greater.
 On the other hand, this function does not guarantee work for Oracle
 version below 11g for the use of several clobs.
 Perhaps it makes sense to abandon support for Oracle versions below 11g in
 Django 1.6 or 1.7.

-- 
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/070.45cce827bdffdcbb64c5a1534e97a5f7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
-+-
 Reporter:  nosrednakram |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |  1.1-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:  oracle TextField | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by CarstenF):

 * cc: carsten.fuchs@… (added)
 * ui_ux:   => 0
 * easy:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
-+-
   Reporter: |Owner:  nobody
  nosrednakram   |   Status:  new
   Type:  Bug|Component:  Database layer
  Milestone: |  (models, ORM)
Version: | Severity:  Normal
  1.1-beta-1 | Keywords:  oracle TextField
 Resolution: |Has patch:  0
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by morgy.wahl@…):

 Thanks. Those return:

 NLS_CHARACTERSET  WE8MSWIN1252

 NLS_NCHAR_CHARACTERSET   AL16UTF16

 and:

 Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit
 Production

 So it seems my NCLOBs are indeed UTF-16, which confirms the 4000-byte
 limit. And, on Oracle 11g at least, just removing the call to
 DBMS_LOB.SUBSTR works.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
-+-
   Reporter: |Owner:  nobody
  nosrednakram   |   Status:  new
   Type:  Bug|Component:  Database layer
  Milestone: |  (models, ORM)
Version: | Severity:  Normal
  1.1-beta-1 | Keywords:  oracle TextField
 Resolution: |Has patch:  0
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by ikelly):

 Replying to [comment:5 morgy.wahl@…]:
 > I have the same problem here. In tests (which may be dependent on my
 data), I didn't get the error for substring lengths of 2000 or less, but
 did for 2001 and greater. I'm not the DBA so I'm not sure how CLOBs are
 encoded, but UTF-16 with a 4000-byte limit would make sense, since all the
 text I'm storing is in the ASCII set (and thus would be 2 bytes per
 character in UTF-16). I'm not sure what Oracle version I'm using. (how can
 I find out?)

 This query will show you your database character set (CLOBs) and your
 national character set (NCLOBs):

 {{{SELECT * FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER IN
 ('NLS_CHARACTERSET', 'NLS_NCHAR_CHARACTERSET');}}}

 This query will show you the database version:

 {{{SELECT * FROM V$VERSION;}}}

 > I tried removing the call to SUBSTR all together, and it worked fine (at
 least, with __icontains).

 Interesting, according to the docs it appears that LIKE is actually
 supported for CLOBs, although = and <> are not.  That will be very useful
 in fixing this.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
-+-
   Reporter: |Owner:  nobody
  nosrednakram   |   Status:  new
   Type:  Bug|Component:  Database layer
  Milestone: |  (models, ORM)
Version: | Severity:  Normal
  1.1-beta-1 | Keywords:  oracle TextField
 Resolution: |Has patch:  0
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by morgy.wahl@…):

 I have the same problem here. In tests (which may be dependent on my
 data), I didn't get the error for substring lengths of 2000 or less, but
 did for 2001 and greater. I'm not the DBA so I'm not sure how CLOBs are
 encoded, but UTF-16 with a 4000-byte limit would make sense, since all the
 text I'm storing is in the ASCII set (and thus would be 2 bytes per
 character in UTF-16). I'm not sure what Oracle version I'm using. (how can
 I find out?)

 I tried removing the call to SUBSTR all together, and it worked fine (at
 least, with __icontains).

 FYI the Oracle docs seem to indicate DBMS_LOB.SUBSTR defaults to an offset
 of 1 and a length of 32767 (i.e. 2^15^ - 1).

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
---+
  Reporter:  nosrednakram  | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.1-beta-1 
 
Resolution:|  Keywords:  oracle 
TextField
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Comment (by nosrednakram):

 Hello,

 Thanks for your quick reply, I did a rough hack based on your information,
 I'll try and get to cleaning up at a later date so I can search the entire
 lob contents and maybe even post a patch.  This will get me by until I can
 come back to this in a week or so unless someone else creates a patch
 first.  This also allowed the searching of lobs within the ADMIN interface
 again.

 I modified django/db/backends/oracle/base.py and gave a size to the
 substr, it didn't have one, FYI.

 WAS:
 {{{
 #!py
 def field_cast_sql(self, db_type):
 if db_type and db_type.endswith('LOB'):
 return "DBMS_LOB.SUBSTR(%s)"
 else:
 return "%s"
 }}}
 NOW:
 {{{
 #!py
 def field_cast_sql(self, db_type):
 if db_type and db_type.endswith('LOB'):
 return "DBMS_LOB.SUBSTR(%s,2000,1)"
 else:
 return "%s"
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
---+
  Reporter:  nosrednakram  | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.1-beta-1 
 
Resolution:|  Keywords:  oracle 
TextField
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by ikelly):

 * cc: mboersma (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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11580: Unable to query TextField against oracle nclob 10Gr4

[Django]

#11580: Unable to query TextField against oracle nclob 10Gr4
---+
  Reporter:  nosrednakram  | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  1.1-beta-1 
 
Resolution:|  Keywords:  oracle 
TextField
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by ikelly):

  * needs_better_patch:  => 0
  * component:  Uncategorized => Database layer (models, ORM)
  * needs_tests:  => 0
  * summary:  Unable to query TextFiled against oracle nclob 10Gr4 =>
  Unable to query TextField against oracle nclob
  10Gr4
  * keywords:  => oracle TextField
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted

Comment:

 This looks like it may be the same error:
 
http://groups.google.com/group/comp.databases.oracle.server/browse_thread/thread/b7950ba7df01b90e

 The apparent solution would be to substr out the first 1000 characters of
 the lob rather than the first 4000 characters like we're doing now.  Or
 better, remove the SUBSTR hack altogether and get TextField lookups
 working using DBMS_LOB.INSTR instead.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---