Re: ** PL/SQL question

From: Jared Still <jkstill_at_cybcon.com>
Date: Sun, 08 Feb 2004 09:42:03 -0800
Message-Id: <1076262123.2838.7148.camel@poirot>

You don't mention what your front end is, but why would that necessitate changing the SQL to retrieve the data to populate the page from a ref cursor to arrays?

Aren't the two are generally mutually exclusive? There may be notable exceptions such as Oracle Forms.

Keep in mind that if you are using ODBC, and happen to be using Oracle's ODBC, you can't use arrays. You will either have to stick to ref cursors, or switch to Microsoft's ODBC driver.

Ironic, isn't it?

Jared

On Fri, 2004-02-06 at 20:04, A Joshi wrote:
> MLaden,
> The maximum rows that will be retrieved is 25. I forgot to mention that this data goes to front end GUI application which the user sees and could modify the data and send it back to be updated in the database.
>
>
> Mladen Gogala <mgogala_at_adelphia.net> wrote:
> To my knowledge, PL/SQL can do "update ...where current of cursor".
> The problem arises when you commit. There is a very popular and
> lovely error called "fetch accross commit".
>
> On 02/06/2004 10:36:10 PM, A Joshi wrote:
> > Hi,
> > I have a stored procedure that returns a set of rows using a ref
> > cursor. Now the user wants the ability to update (any field other
> > than
> > primary key) and send back the data and it should update the rows. I
> > will probably have to switch to arrays. Any precautions I need to
> > take? Does anyone have an example for this? Thank you
> >

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Sun Feb 08 2004 - 11:42:03 CST