Cloudscape (the codeline which Derby is based on) used to include
user-defined aggregates, which you could declare with a CREATE AGGREGATE
statement. DERBY-672 tracks the effort to put user-defined aggregates
into Derby. It sounds as though you might want to volunteer for this
effort. That
Williamson, Nick wrote:
Hi all,
In Oracle, when you want to update a BLOB, you have to do this first:
set my_blob_column=empty_blob();
...which initializes it and opens it up for writing. Oracle has a
concept of a locator, which I guess is similar to a pointer or
handle to the BLOB
Rick Hillegas wrote (2007-11-02 05:21:09):
Hi Jon,
The situation with case-insensitive searching did not change in the
latest 10.3 release and no one has volunteered to address this issue in
the next feature release, 10.4. If you want to avoid the full table
scan, you can store the text
Very nice! Is Java DB embedded in the applet, or used solely on the
server side?
David
On Oct 31, 2007 2:41 PM, David Leader [EMAIL PROTECTED] wrote:
I found the replies to my query interesting. I guess I need to ask my
son why he favours SQLite. I much prefer to stick with a Java-based
Bernt M. Johnsen wrote:
Rick Hillegas wrote (2007-11-02 05:21:09):
Hi Jon,
The situation with case-insensitive searching did not change in the
latest 10.3 release and no one has volunteered to address this issue in
the next feature release, 10.4. If you want to avoid the full table
scan,
Daniel John Debrunner wrote:
Bernt M. Johnsen wrote:
Rick Hillegas wrote (2007-11-02 05:21:09):
Hi Jon,
The situation with case-insensitive searching did not change in the
latest 10.3 release and no one has volunteered to address this issue
in the next feature release, 10.4.
See
Hello,
I wish to see an example of how to write a DerbySQLroutines aggregate
function. My idea is to write a commaDelim() function that will
comma delimit an aggregated column in a group by sql.
Thanks,
Mike Bushman | Director, Product Development
WingateWeb .::: The Event Technology
Hi Jon,
The situation with case-insensitive searching did not change in the
latest 10.3 release and no one has volunteered to address this issue in
the next feature release, 10.4. If you want to avoid the full table
scan, you can store the text in two columns: mixed case in one column,
and
thank you for pointing out the request with the not exists syntax
for some reason i won't use the except syntax since i would have te
write almost twice the same request
i was stuck with not in since it was working with oracle
it was confusing
thank you very much
Tyoup
oysteing wrote:
