Re: LONG/LONG RAW Limitation

I do not know anything about oracle oledb provider limitations, but one thing I can say for sure: get rid of LONGs ASAP. It's the most limited thing Oracle has (second is IOTs). Change them to LOBs. Oracle oledb works fine with them, and LOBs don't have most of the limitations LONGs impose, including single LONG per table, lack of proper support in SQL (including DDL), etc.

--
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.


"Nirmal TS" <nirmal.ts_at_in.bosch.com> wrote in message news:a0cj8h$pj9$1_at_ns2.fe.internet.bosch.com...


> hi

>

> I have a stored procedure which returns via an out array parameter LONG RAW


> as chunks of 4k..and the total size of the parameter is above 32k...MS

> OLEDB for Oracle has documented a limitation of 32k for in/out parms when

> used in stored procedures but not with select/insert/update statements.

> (Ref: MSDN/Microsoft OLE DB Provider for Oracle Tips, Tricks and Traps:

> LONG/LONG RAW Limitations)

>

> I want to know if there's any limitation when using oraOLEDB?

>

> rgds

> Nirmal

>

>

>