Code

Opened 5 years ago

Closed 5 years ago

Last modified 3 years ago

#10473 closed (fixed)

Add support for "RETURNING" to Oracle backend.

Reported by: ikelly Owned by: nobody
Component: Database layer (models, ORM) Version: master
Severity: Keywords: oracle returning
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

We should take advantage of the framework's new support for "RETURNING" clauses.

Attachments (0)

Change History (4)

comment:1 Changed 5 years ago by ikelly

  • milestone changed from 1.1 to 1.1 beta
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

comment:2 Changed 5 years ago by ikelly

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

(In [10044]) Fixed #10473: Added Oracle support for "RETURNING" ids from insert statements.

comment:3 Changed 5 years ago by mboersma

Unfortunately, this is only supported in Oracle 10g and later. In 9i (which our common employer happens to use still), it returns this error:
ORA-22816: unsupported feature with RETURNING clause

So we either need a workaround here, or should specify that only Oracle 10g and later are supported in Django 1.1.

comment:4 Changed 3 years ago by jacob

  • milestone 1.1 beta deleted

Milestone 1.1 beta deleted

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.