#5543: cursor.callproc with oracle backend does not work
-------------------------------------+--------------------------------------
Reporter:  [EMAIL PROTECTED]  |       Owner:  nobody             
  Status:  new                       |   Component:  Database wrapper   
 Version:  SVN                       |    Keywords:  oracle, db, backend
   Stage:  Unreviewed                |   Has_patch:  0                  
-------------------------------------+--------------------------------------
 When using cx_oracle standalone, in order to call stored procedures, it is
 possible to call them using callproc(), which does some jobs including
 using bind variables for you. However, in django's
 FormatStylePlaceholderCursor wrapper class, there is no callproc(). That
 means that calling callproc() as a member of a
 FormatStylePlaceholderCursor cursor will call the original cx_oracle
 callproc(). This in turn uses django's execute(). It is probably expecting
 the behaviour of the original execute.
 In this case the query is however not to be changed. Maybe a solution is
 to add a callproc function to the wrapper class and let it duplicate
 cx_oracle's callproc so it works with djangos parameters.

 The error raised is:
 {{{
  File "/usr/lib/python2.5/site-packages/django/db/backends/oracle/base.py"
 in execute
   483. query = smart_str(query, self.charset) % tuple(args)

   TypeError at /test/ora_django/
   not all arguments converted during string formatting
 }}}

-- 
Ticket URL: <http://code.djangoproject.com/ticket/5543>
Django Code <http://code.djangoproject.com/>
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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to