Opened 8 years ago

Closed 8 years ago

Last modified 5 years ago

#7637 closed (fixed)

Allow Oracle database parameters to specify input size.

Reported by: jbronn Owned by: mtredinnick
Component: Database layer (models, ORM) Version: master
Severity: Keywords: oracle backend clob nclob
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


Currently, the Oracle backend sets the input size to NCLOB for character input > 4000 characters. In GeoDjango, geometry input text is passed into the SDO_UTIL.TO_WKTGEOMETRY stored procedure, which expects input of type CLOB.

This patch allows database parameters to specify their input size via an input_size attribute, that will be used for setinputsizes instead of the default (if it exists). This functionality was added to the gis branch in r7637, and needs to be in trunk for GeoDjango to work on Oracle when the branches merge for 1.0.

Attachments (1)

orcl_custom_input_size.diff (4.0 KB) - added by jbronn 8 years ago.
Patch that allows Oracle database parameters to specify input size.

Download all attachments as: .zip

Change History (4)

Changed 8 years ago by jbronn

Patch that allows Oracle database parameters to specify input size.

comment:1 Changed 8 years ago by mtredinnick

  • Needs documentation unset
  • Needs tests unset
  • Owner changed from ikelly to mtredinnick
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Ready for checkin

jbronn tells me he and ikelly have already discussed this offline and it's considered reasonable.

comment:2 Changed 8 years ago by mtredinnick

  • Resolution set to fixed
  • Status changed from new to closed

(In [8145]) Fixed #7637 -- Added an extra parameterisation hook to the Oracle backend.
Required for some extension modules (in particular, geo-django). Patch from
Justin Bronn.

comment:3 Changed 5 years ago by jacob

  • milestone 1.0 beta deleted

Milestone 1.0 beta deleted

Note: See TracTickets for help on using tickets.
Back to Top