Opened 17 years ago

Closed 17 years ago

Last modified 13 years ago

#7637 closed (fixed)

Allow Oracle database parameters to specify input size.

Reported by: jbronn Owned by: Malcolm Tredinnick
Component: Database layer (models, ORM) Version: dev
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: no UI/UX: no
Pull Requests:How to create a pull request

Description

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.

Change History (4)

by jbronn, 17 years ago

Attachment: orcl_custom_input_size.diff​ added

Patch that allows Oracle database parameters to specify input size.

comment:1 by Malcolm Tredinnick, 17 years ago

Owner: changed from Erin Kelly to Malcolm Tredinnick
Triage Stage: Unreviewed → Ready for checkin

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

comment:2 by Malcolm Tredinnick, 17 years ago

Resolution: → fixed
Status: new → 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 by Jacob, 13 years ago

milestone: 1.0 beta

Milestone 1.0 beta deleted

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