0022875: Translations from Oracle to PostgreSQL is not supported for some cursor declarations.

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0022875

Openbravo ERP

Y. DBSourceManager

public

2013-01-23 16:55

2013-01-23 23:35

Reporter

ioritzCia

Assigned To

marvintm

Priority

normal

Severity

major

Reproducibility

have not tried

Status

new

Resolution

open

Platform

OS Version

Ubuntu 10.04

Product Version

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0022875: Translations from Oracle to PostgreSQL is not supported for some cursor declarations.

Description

Depending the way a cursor is declared in a database function/procedure, DBSourceManager does not handle the translation. The syntax not supported is the following one:

  Cur_Something RECORD; --> in Oracle
  DECLARE Cur_Something REFCURSOR; --> in PostgreSQL

If the cursor is going to be opened with the following sentence in both languages:

  OPEN Cur_Something FOR SELECT whatever FROM wherever ...;

This is related with issue 22086. There is a slow LOOP structure cursor there that can be improved using separate cursors with the previous structure. The proposed solution in that issue does not work because LOOP cursor types fail in PostgreSQL while opening them twice recursively giving an error that says that it is not possible to open an already opened cursor.

For other cursor declarations <Cur_Something RECORD;> is the right way to do declare a cursor, but for the ones explained previously PostgreSQL requires <DECLARE Cur_Something REFCURSOR;> and Oracle <Cur_Something RECORD;>

Steps To Reproduce

Follow the description.

Proposed Solution

Additional Information