Thanks, I will play with that!
-Original Message-
From: Satheesh Bandaram [mailto:[EMAIL PROTECTED]
Sent: Fri 1/13/2006 3:20 PM
To: derby-dev@db.apache.org
Subject: Re: VTI, Indexed Lookup and the Query Optimizer
Jeffrey Lichtman wrote:
The optimizer should consider hash join on a
Thanks for the feedback.
I have another clue to share about the poor performance. If I use an
INNER JOIN to join two VTIs, the performance is absolutely terrible. If
I use the equivalent FROM and ID=ID syntax, it works OK (not great,
but OK).
Also, we register our VTI tables as VIEWs and join
Was the syntax CREATE VIRTUAL TABLE implemented with these
changes, or are they hard-wired for internal tables only now?
From: Myrna van
Lunteren [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 19, 2005
2:26 AM
To: derby-dev@db.apache.org
Subject: Re: [jira] Closed:
I for one, see the power of this feature and welcome it back in the
fold. We are moving in a direction that would either 1) place our own
VTIs under the diag namespace (ugly) or 2) shipping a slightly modified
form (ugly) or 3) petitioning to get this added back in.
The VTI API should have the
Actually, I found that in the case of LIKE 'Smith%', it pushes two
qualifiers, broken into a and operator, or something strange like
that.
I see the commented out handleQualifier. I'm not sure what to make
of that.
I'm also thinking I could propose the easy fix, which is to make using
