× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Vernon,

Your result would have been instant because you didn't specify a where clause.

do you think set :$itemfound (select 1...
  will be faster than

  select '1' into :$itemfound.....

?

thanks,

Rick

On 4/18/06, vhamberg@xxxxxxxxxxx <vhamberg@xxxxxxxxxxx> wrote:
> Try pasting the following into an SQLRPGLE source and substitute your library 
> and file for qiws/qcustcdt. I ran it over a file with c.350,000 records, it 
> was instant.
>
> di                s              1p 0
> c/exec sql
> c+ set :i = (select 1 from sysibm/sysdummy1
> c+           where exists(select * from qiws/qcustcdt))
> c/end-exec
> c                   eval      *inlr = *on
>
> -------------- Original message --------------
> From: "rick baird" <rick.baird@xxxxxxxxx>
>
> > hey all,
> >
> > Is there a way to run an SQL statement that doesn't (necessarily)
> > return anything, but only checks for the existence of one or more
> > records based on a where statement - similar to a SETLL and %found?
> >
> > I've got a rather complicated SQL statement using:
> > LIKE '___abc___' or it could be:
> > LIKE ______xyz'
> >
> > - over a very large file, and I'm having performance issues.
> >
> > I don't want to do a count(), because I don't care how many, only that
> > at least one exists. with count, it would have to read through the
> > entire file to determine it.
> >
> > I also tried just doing a select - optimize for 1 row and a single
> > fetch, but that seemed to take forever too. It appears as if it is
> > searching the entire file, instead of stopping at the first one.
> >
> > help!
> >
> > Rick
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.