Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Error 38000 with a stack overflow on recordset.next()?
Date: Thu, 20 Oct 2005 16:04:34 -0400
Message-ID: <411004C89F48004A9B41C341A515E7BA01A3D176@mail.oit.docfinity.com>
Thread-Topic: Error 38000 with a stack overflow on recordset.next()?
Thread-Index: AcXVqqetL7qnPSvwTXireNkVVCUZiwABqhnw
From: "Daniel Skiles" <dskiles@docfinity.com>
To: "Derby Discussion" <derby-user@db.apache.org>

-----Original Message-----
From: Jeffrey Lichtman [mailto:swazoo@rcn.com]=20
Sent: Thursday, October 20, 2005 3:15 PM
To: Derby Discussion
Subject: RE: Error 38000 with a stack overflow on recordset.next()?

Here's a potential workaround for your problem. I suspect it will=20
work, but I'm not sure:

SELECT path from filesystemfiles where not exists
         (select * from existingfiles where existingfiles.path =3D=20
filesystemfiles.path)

The query does the same thing as your original one with "not in", but=20
I suspect Derby will not try to use the in-memory optimization I=20
mentioned in my previous mail.


Jeff,
That works perfectly.  Thanks for the help.

Daniel