Re: WebDB: Why won't these 2 queries work in a report?

Yes, there's a limit of 2000 characters. For passing parameters and values between the various packages webdb uses pl/sql-tables of type vc_arr. In the pl/sql web-toolkit (by default installed in schema oas_public) in package owa this type is declared as:

   type vc_arr is table of varchar2(2000) index by binary_integer;

Funny thing (now it's funny - when we first experienced it it was a mess) with webdb 2.1 in 8.1.5 on HP-UX 64 bit: When your query was too long in the report definition and you had installed the scott schema, webdb came back with an error message (parse error although the statement worked perfectly in sql*plus) when switching from the query screen to the fields screen. When you returned to the query screen webdb had replaced your long query - that was so cumbersome to type - with just a new query: select * from scott.emp!!! We dropped scott and could at least preserve our long statement that we had to cram into a view.

By the way: Never try to "format" your query with carriage returns - webdb doesn't like that.

Klaus

"Kelly" <kgrigg_at_diamonddata.com> schrieb im Newsbeitrag news:8l22mr$vtg$1_at_nnrp1.deja.com...
> Hello all,
> I'm just testing creating my own 'links' and am puzzled. I created two
> links with the wizards. Both links work...then to test a theory...I cut
> and pasted the example queries that the link got into a test report. I
> cut and pasted exactly from these two working links. The first one that
> is looking at the the 'system' table in my schema works...but, the exact
> query looking at the organization table...does not...gives and
> error...(not only that...the screen says error...but, displays nothing
> else...
>
> Is there some kind of limit on the size of a select statement that WebDB
> can parse?
>
> The first one that works is:
>
>
> select '<A
> HREF="'||'LI_TRACKER.FORM_KELLY_SYSTEMS.SHOW?p_arg_names=_show_header&p_
> arg_values=YES&p_arg_names=_rowid&p_arg_values='||WEBDB.wwv_standard_uti
> l.url_encode(ROWID)||'&p_arg_names=_alt_rowid&p_arg_values='||WEBDB.wwv_
> standard_util.url_encode(ROWID)||'">'||SYSTEM.ROWID||'</A>'
> from LI_TRACKER.SYSTEM
>
> The second one that fails...and leaves a blank screen is:
>
>
> select '<A
> HREF="'||'LI_TRACKER.FORM_ORGANIZATIONS.SHOW?p_arg_names=_show_header&p_
> arg_values=YES&p_arg_names=_rowid&p_arg_values='||WEBDB.wwv_standard_uti
> l.url_encode(ROWID)||'&p_arg_names=_alt_rowid&p_arg_values='||WEBDB.wwv_
> standard_util.url_encode(ORGANIZATION_ID)||'">'||ORGANIZATION.ROWID||'</
> A>'
> from LI_TRACKER.ORGANIZATION
>
> Any ideas why both don't work when cut and pasted into the SQL portion
> of a report?
>
> TIA!!
>
> Kelly
> kgrigg_at_diamonddata.com
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>
Received on Tue Jul 18 2000 - 00:00:00 CEST