I have made a test and dropped the composite index, and now the
sorting is ok, regenerated the index and sorting is as described
in my first problem report.
tom
It seems likely that the optimizer is using the index as a
sort-avoidance strategy. That is, it is recognizing that the index is
i
Thank you very much for reading my post.
can you please explain me what is differences between 1 index for
one column and one index for multiple columns ?
In addition to what Ryan Bobko has already said about SELECT
statements, I should point out that the existence of indexes on a
table aff
This is a repeat of my vote, which I previously sent only to derby-dev:
Logo candidates (place an X by your choice).
10. [X] (these all belong together...)
http://issues.apache.org/jira/secure/attachment/12321022/derby_logo_only.jpg
http://issues.apache.org/jira/secure/attachment/12321023/derb
If you look at Roger's initial post and open the attachment you will see
that he addressed the issues you mentioned: small size of logo, black and
white logo.
My point is that voters should take this into account, not that any
submitter didn't.
-Jeff Lichtman
What's a "favicon"?
David
A favicon is a very small graphic file that is associated with a web
site. A browser will usually display it in the upper left corner of a
page or tab window. The resolution of a favicon is usually 16 by 16 pixels.
The Google favicon is a blue capital G in a whit
There was an aborted logo contest earlier this year. What happened to
the entries? Should they be submitted to the current contest?
Also, what form will the voting take and how will a winner be
determined? The usual way to run an election is to let every voter
pick one candidate, and for the w
I've described the problem in detail below, and I'd appreciate any
assistance. Specifically:
i) Does anyone have any plans to fix this problem?
I believe the real problem is that Derby doesn't have any strategy
for doing multiple scans for OR/IN clauses. This is a useful feature,
but I don
> If you want to get the count including nulls, you can use COUNT(*),
> which returns the number of rows in the set being aggregated (not the
> number of values).
A side question: Is this any faster than using COUNT( colName)? Or
does COUNT() always entail something on the order of iterating
1) A null column is excluded from a COUNT( colName ) aggregate. This
is described in the section 10.9 under General Rules 4a. The
database is supposed to raise a warning: "warning--null value
eliminated in set function"
If you want to get the count including nulls, you can use COUNT(*),
whi
I don't have my copy of the X3H2 SQL standard in front of me, but as
I remember, the rule for unique constraints is that the uniqueness is
applied only to non-null values. The standard is not available
on-line (ANSI/ISO protects its copyright vigorously), but I did find
a web site that backs me
Here's a potential workaround for your problem. I suspect it will
work, but I'm not sure:
SELECT path from filesystemfiles where not exists
(select * from existingfiles where existingfiles.path =
filesystemfiles.path)
The query does the same thing as your original one with "not in", b
I believe I've figured out what's going on with this bug. It involves
an optimization to materialize subquery results in some cases. This
optimization works by creating a nested union of in-memory rows.
What's happening in this case is that the unions are nested so deep
that it gets a stack ove
Its a nice goal to be zero admin. however, I wonder if you're implying
something that may be misleading.
Good point - this needs clarification. The idea of zero admin with
Derby is that an application doesn't need maintenance once it's
deployed. It doesn't mean that no tuning is required - j
I start out by running the following prepared statement a few thousand
times:
INSERT into existingfiles (path, id) VALUES (?, ?)
Where path is a windows file path and id is an integer. I clear out the
parameters with clearParameters() after each insert and set them to new
values. Then I clos
. . . if I issue a very large, expensive select * from huge_table, if I
have server side cursors, response is immediate, because there is nothing
to process. My cursor is just a pointer to real data in the table.
Even if I make a select * from huge_table order by some_column, if the
column i
I can't seem to find a way to get the number of rows in the
current result via JDBC. Is there a way to get the number of
rows in the result?
There is no such method, mainly because it is impossible for a DBMS to know
in advance how many rows will be in the result, except
When I first looked at Cloudscape years ago, I could have sworn there was
support for Java objects and data types in a table definition, and you
could refer to methods and fields in your SQL statements. Was I dreaming,
or did it get removed?
You weren't dreaming. IBM removed it in the version
Just a thought: what will we do if someone stuffs the ballot box on this
vote the same way they did on the original vote?
-Jeff Lichtman
[EMAIL PROTECTED]
Check out Swazoo Koolak's Web Jukebox at
+1 Reject the tally. New method of choosing a logo is determined by the
community.
-Jeff Lichtman
[EMAIL PROTECTED]
Check out Swazoo Koolak's Web Jukebox at
http://swazoo
The sudden flood of votes for a specific logo yesterday looked kind of
odd, especially the one from "noname nolastname", and I'm concerned we
might be getting votes from people who joined the list just to cast a vote.
But maybe it's just me -- has anyone else thought anything odd?
-jean
My fir
[ ] 32
[X] 35
[ ] None of the above - keep trying
-Jeff Lichtman
[EMAIL PROTECTED]
Check out Swazoo Koolak's Web Jukebox at
http://swazoo.com/
[ X] 35
-Jeff Lichtman
[EMAIL PROTECTED]
Check out Swazoo Koolak's Web Jukebox at
http://swazoo.com/
The simple majority of votes will determine the winner.
Do you mean a simple majority or a plurality? With the number of entries,
it's not likely that there will be a simple majority (i.e. an entry whose
votes account for more than 50% of those cast). There are several ways to
deal with this:
I have a field decimal(10,2) where I insert "32,78", but when I go
to look at in the table the inserted value was "32,77", alguem which
the problem?
This is probably caused by the fact that you are inserting the value as a
double. Doubles are not exact values - my guess is that 32.78 is being
With automcommit == true, is an INSERT always treated as single
transaction, even if the INSERT inserts multiple rows of data? I've
always assumed that this would be the case, but I'm not sure I've seen
that in it the jdbc autocommit contract. The practical question is
whether I should turm
I'm trying to create a stored function in Derby and call it from either ij
or Java. The class I created is:
package oi;
import java.sql.*;
public class Derby
. . .
ij> create function earthlings.build_email (firstname varchar(20),
lastname varchar(30))
returns varchar(8)
language java
external
The SQLite folks have been trying
to compare it with Derby, see
http://www.sqlite.org/cvstrac/wiki?p=SqliteVersusDerby,
although (by
their own admission) they don't have a deep understanding of Derby.
Is
their evaluation correct?
Thanks,
David
These parts are definitely incorrect:
--
27 matches
Mail list logo
