I have checked the values in the database, they have no leading spaces.
The names are only a simple example for describing the problem, the
data structure is more complex and the query has joins and conditions.
This query was working with other dbms but it had no composite index,
I have added the
this is working
select col from table where lower(col) like '%something%'
this is not
select col from table where lower(col) like '%something'
try it with value in database = XXXsomething
seems like derby auto generates trailing blanks
tom
Thomas Vatter [EMAIL PROTECTED] writes:
this is working
select col from table where lower(col) like '%something%'
this is not
select col from table where lower(col) like '%something'
try it with value in database = XXXsomething
seems like derby auto generates trailing blanks
You
I understand, I'll change the code. the code had worked with other
dbms, but no problem to change it
tom
Knut Anders Hatlen wrote:
Thomas Vatter [EMAIL PROTECTED] writes:
this is working
select col from table where lower(col) like '%something%'
this is not
select col
Hi, as noted on the Apache Derby community page
(http://db.apache.org/derby/derby_comm.html):
Derby uses Apache's Jira issue tracker
(http://db.apache.org/derby/DerbyBugGuidelines.html) to log bugs and
enhancement requests. Anyone can browse the Jira database. To log new
issues, see the tips
I have a DB (Derby)
having 100's thousands of rows. I would like to select row using a condition and
be able to page them. The problem is that if I page them in memory I get an
outofmemory error or the rowset returns a couple of thousands instead of all the
rows matching the condition.
Is
Thomas Vatter wrote:
A clustered index should be the fastest access for retrieving ordered
columns. 'Create index' command does not yet support it. Since ordering
is my main problem at the moment I post this as request for enhancement.
What do you mean by a clustered index? It usually means
Zithulele Basil Shange wrote:
I have a DB (Derby) having 100's thousands of rows. I would like to
select row using a condition and be able to page them. The problem is
that if I page them in memory I get an outofmemory error or the rowset
returns a couple of thousands instead of all the rows
yes, with varchar it works fine
Knut Anders Hatlen wrote:
Thomas Vatter [EMAIL PROTECTED] writes:
this is working
select col from table where lower(col) like '%something%'
this is not
select col from table where lower(col) like '%something'
try it with value in database
I have a function to round a Double to a specified number of decimal places:
public static final Double derbyDouble (Double value, Integer places) {
...
}
I've declared it to Derby like so:
CREATE FUNCTION DoubleFormat (value FLOAT,
places INTEGER)
John English wrote:
I have a function to round a Double to a specified number of decimal
places:
public static final Double derbyDouble (Double value, Integer places) {
...
}
I've declared it to Derby like so:
CREATE FUNCTION DoubleFormat (value FLOAT,
Jean T. Anderson wrote:
John English wrote:
I have a function to round a Double to a specified number of decimal
places:
public static final Double derbyDouble (Double value, Integer places) {
...
}
I've declared it to Derby like so:
CREATE FUNCTION DoubleFormat (value FLOAT,
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
hi all, i have created a table in derby as follow create table sp_ss_ex_contact( email varchar(200) primary key, first_name varchar(50) not null , middle_name varchar(50) , last_name varchar(50) not null ,telephone varchar(20 ) , address varchar(250) , state char (1 ) not null , last_update
if i'm not misunderstood your explanation, tats mean i have to store ex: 2006-10-31 to 3 different columns, (Yr) for 2006, (Mth) for 10 and (Dy) for 31.By this way i can use the function GROUP BY for those columns.
Anyway, will it be any enhancement for function GROUP BY in future?Thanks Stanley.
tom wrote:
I mean an index that kept up to date on disk permanently. This is the definition
that I know from the time I was using Informix Online. The syntax was 'create
clustered index ...'. I don't mean to put it on the primary key as SQL-Server
does, but having the possibility to create one
16 matches
Mail list logo
