Re: arrays and Oracle

That's what I've been telling you: nested tables are more suitable for this IMO. They act like master-detail-related tables, but are presented as a single entity to the client. Even if number of child elements is always the same, nested tables are still more effective.

As of pro*c crashing on including oci.h - sounds like a bug to me. Be sure to install the latest patchset on both server and client and try compiling again.

--
Vladimir Zakharychev (bob_at_dpsp-yes.com)                http://www.dpsp-yes.com
Dynamic PSP(tm) - the first true RAD toolkit for Oracle-based internet applications.
All opinions are mine and do not necessarily go in line with those of my employer.


"Tomasz Wojcik" <wojcik_at_psja1.if.uj.edu.pl> wrote in message
news:3C6D5BC6.9080306_at_psja1.if.uj.edu.pl...


> Hi!

> Vladimir M. Zakharychev wrote:

> > How about using nested tables instead of varrays?


> I want to store only integer number as the array. I know exactly the

> size of those arrays.

> So I thing that for me better is the varray. The point is that I can't

> insert data from my proC/C++ code.

> I used "ott" to translate object type and when I tried  to compile the

> code I got some troubles.

> The "proc" was crashed always when oci.h was included.

> The question is if there is better solution to store int arrays i Oracle

> regards

> TW.

>