db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satheesh Bandaram (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-384) Doc Review: Tuning Derby
Date Fri, 24 Jun 2005 02:08:22 GMT
    [ http://issues.apache.org/jira/browse/DERBY-384?page=comments#action_12314380 ] 

Satheesh Bandaram commented on DERBY-384:

Well... I think you shouldn't be able to create an index on long varchar for bit data... That
seems to be a bug... Derby doesn't allow creating indexes on long varchar, so why this favouritism
for bit data?

ij> create table TBIGINT(id bigint, c long varchar);
0 rows inserted/updated/deleted
ij> create index id2 on tbigint(c);
ERROR X0X67: Columns of type 'LONG VARCHAR' may not be used in CREATE INDEX, ORDER BY, GROUP
BY, UNION, INTERSECT, EXCEPT or DISTINCT statements because comparisons are not supported
for that type.
ij> create table TBIGINT1(id bigint, c long varchar for bit data);
0 rows inserted/updated/deleted
ij> create index id2 on tbigint1(c);
0 rows inserted/updated/deleted

> Doc Review: Tuning Derby
> ------------------------
>          Key: DERBY-384
>          URL: http://issues.apache.org/jira/browse/DERBY-384
>      Project: Derby
>         Type: Improvement
>   Components: Documentation
>  Environment: all
>     Reporter: Jeff Levitt
>     Priority: Minor
>      Fix For:

> This issue tracks comments for the manual known as Tuning Derby. The deadline for posting
comments is Tuesday, June 28, noon Pacific time.
> Some guidelines to follow when posting comments to this issue are:
> - Try to make clear and concise comments about what you want changed whenever possible.
 Provide concrete comments that say "Please change <original> to <modified>" instead
of generic comments like "This section needs to be rewritten."
> - If you're reviewing the HTML Files copy, include the URL for the page in the review
comment. Obtain the URL like this:
>     * highlight the topic in the left frame
>     * right click
>     * choose "Properties"
>     * copy and paste the address in the pop up box.
> - If you're reviewing the PDF copy, in the review comment:
>     * Include the page number for the PDF, and indicate whether the number is the PDF
sheet number or the printed page number.
>     * Include the title of the section that the problem occurs in. If it's in a subsection,
try to include the hierarchy of titles.
> - Please don't review the HTML Book copy -- it'll be time consuming to match up that
copy with the underlying DITA source.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message