[
http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12315870 ]
Rick Hillegas commented on DERBY-289:
-
I confess I'm still puzzled. It seems to me there may be two separate issues
here: 1) the interoperability of different derby version
Full Text Indexing / Full Text Search
-
Key: DERBY-472
URL: http://issues.apache.org/jira/browse/DERBY-472
Project: Derby
Type: New Feature
Components: SQL
Versions: 10.0.2.0
Environment: All environments
Reporter:
[ http://issues.apache.org/jira/browse/DERBY-171?page=all ]
Rick Hillegas reassigned DERBY-171:
---
Assign To: Rick Hillegas
Grabbing this bug.
> Need Correlation ID in UPDATE/DELETE statements
> ---
>
>
[ http://issues.apache.org/jira/browse/DERBY-171?page=all ]
Rick Hillegas updated DERBY-171:
Attachment: bug171.diff
bug171.html
I am attaching the subversion diffs for my fix to this bug: bug171.diff. I am
also attaching a description o
[ http://issues.apache.org/jira/browse/DERBY-171?page=all ]
Rick Hillegas updated DERBY-171:
Description:
You currently can't use a correlation ID in an UPDATE/DELETE statement. This
makes it cumbersome to do the following:
UPDATE EMPLOYEE_BONUS
SET
[ http://issues.apache.org/jira/browse/DERBY-396?page=all ]
Rick Hillegas updated DERBY-396:
Comment: was deleted
> Support for ALTER STATEMENT to DROP , MODIFY, RENAME a COLUMN
> --
>
>
[ http://issues.apache.org/jira/browse/DERBY-396?page=all ]
Rick Hillegas updated DERBY-396:
Comment: was deleted
> Support for ALTER STATEMENT to DROP , MODIFY, RENAME a COLUMN
> --
>
>
[ http://issues.apache.org/jira/browse/DERBY-171?page=all ]
Rick Hillegas updated DERBY-171:
Attachment: bug171.diff
Second rev of bugfix. Incorporates Army's feedback: 1) Removes
FromBaseTable.java, which had a vacuous diff, 2) Moves regression tests i
[ http://issues.apache.org/jira/browse/DERBY-499?page=all ]
Rick Hillegas reassigned DERBY-499:
---
Assign To: Rick Hillegas
> Expose BOOLEAN datatype to end users
>
>
> Key: DERBY-499
> URL: http://i
[ http://issues.apache.org/jira/browse/DERBY-156?page=all ]
Rick Hillegas resolved DERBY-156:
-
Resolution: Fixed
This is fixed by submission 231366, which also resolved the linked bug 171.
> Delete with alias on column fails
> -
[
http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12319405 ]
Rick Hillegas commented on DERBY-289:
-
Please also ignore this dummy comment, again added to see if it triggers JIRA
mail.
> Enable code sharing between Derby client and e
[
http://issues.apache.org/jira/browse/DERBY-231?page=comments#action_12319649 ]
Rick Hillegas commented on DERBY-231:
-
I'm a little confused about why Derby allows a FOR UPDATE clause on naked
SELECT statements. I would appreciate a pointer to where th
[
http://issues.apache.org/jira/browse/DERBY-231?page=comments#action_12319792 ]
Rick Hillegas commented on DERBY-231:
-
Roy Lyseng has traced the tortuous path through the SQL spec which allows this
syntax:
part 3 - "Call level interface" chapter 6.50
Re-enable national character datatypes
--
Key: DERBY-533
URL: http://issues.apache.org/jira/browse/DERBY-533
Project: Derby
Type: New Feature
Components: SQL
Versions: 10.1.1.0
Reporter: Rick Hillegas
SQL 2003 coy
[
http://issues.apache.org/jira/browse/DERBY-533?page=comments#action_12319919 ]
Rick Hillegas commented on DERBY-533:
-
1) There are some interesting issues here. Let's say that we re-enable these
datatypes in 10.2. What happens when a client applicatio
[
http://issues.apache.org/jira/browse/DERBY-353?page=comments#action_12320516 ]
Rick Hillegas commented on DERBY-353:
-
The patch looks good but derbyall fails with diffs in derbylang/autoincrement.
Was a canon left out of the patch?
> It is desirable
[
http://issues.apache.org/jira/browse/DERBY-504?page=comments#action_12320737 ]
Rick Hillegas commented on DERBY-504:
-
This is a clean, compact bug fix. It could be made a little more compact:
SelectNode and ProjectRestrictNode have almost identical wh
[
http://issues.apache.org/jira/browse/DERBY-353?page=comments#action_12320741 ]
Rick Hillegas commented on DERBY-353:
-
Derbyall now runs cleanly. Satheesh, can you commit this patch now? Thanks-Rick
> It is desirable to have IDENTITY_VAL_LOCAL() functi
[
http://issues.apache.org/jira/browse/DERBY-504?page=comments#action_12320805 ]
Rick Hillegas commented on DERBY-504:
-
The patch seems to be broken. I can't apply the changes to the j2me canons.
Here's the output from applying the patch:
patching file
[
http://issues.apache.org/jira/browse/DERBY-504?page=comments#action_12320834 ]
Rick Hillegas commented on DERBY-504:
-
Looks great. Derball passes. Ready for a committer to check in.
> SELECT DISTINCT returns duplicates when selecting from subselects
>
[
http://issues.apache.org/jira/browse/DERBY-551?page=comments#action_12320915 ]
Rick Hillegas commented on DERBY-551:
-
Cloudscape 3.5 allowed the CALL statement (procedure invocation) inside a
trigger. So the plumbing to do this is mostly already in th
[
http://issues.apache.org/jira/browse/DERBY-562?page=comments#action_12324452 ]
Rick Hillegas commented on DERBY-562:
-
RawToBinaryFormatStream.checkSufficientData() requires that the InputStream not
have any extra bytes in it. The comment in the code s
Misleading parser diagnostics
-
Key: DERBY-565
URL: http://issues.apache.org/jira/browse/DERBY-565
Project: Derby
Type: Bug
Reporter: Rick Hillegas
Priority: Minor
Bryan Pendleton reports:
When I mistype 'join' as 'joing', the e
[
http://issues.apache.org/jira/browse/DERBY-562?page=comments#action_12324474 ]
Rick Hillegas commented on DERBY-562:
-
You could kludge around this Derby behavior by wrapping your InputStream in a
subclass of java.io.FilterInputStream which truncates i
wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA
Key: DERBY-570
URL: http://issues.apache.org/jira/browse/DERBY-570
Project: Derby
Type: Bug
Components: Documentation
Versions: 10.1.1.0
[
http://issues.apache.org/jira/browse/DERBY-573?page=comments#action_12329897 ]
Rick Hillegas commented on DERBY-573:
-
It sounds as though this syntax will not allow the parser to catch typos and
that if the user makes a mistake, the parser will silent
Grouped select from temporary table raises null pointer exception in byte code
generator
Key: DERBY-578
URL: http://issues.apache.org/jira/browse/DERBY-578
Project: Derby
Type:
[
http://issues.apache.org/jira/browse/DERBY-573?page=comments#action_12330018 ]
Rick Hillegas commented on DERBY-573:
-
Thanks, Mamta, for pointers to these two threads. There is some discussion here
about where to put optimizer threads and how to bind
Mismatch between DatabaseMetaData and ResultSetMetaData for NUMERIC type
Key: DERBY-584
URL: http://issues.apache.org/jira/browse/DERBY-584
Project: Derby
Type: Bug
Reporter: Rick Hillegas
[ http://issues.apache.org/jira/browse/DERBY-516?page=all ]
Rick Hillegas reassigned DERBY-516:
---
Assign To: Rick Hillegas
> Need to incorporate client backward/forward compatibility testing into
> testing procedures.
> ---
[
http://issues.apache.org/jira/browse/DERBY-587?page=comments#action_12331271 ]
Rick Hillegas commented on DERBY-587:
-
This patch looks good to me. I recommend that a committer check it in.
> Providing JDBC 4.0 support for derby
> -
[
http://issues.apache.org/jira/browse/DERBY-587?page=comments#action_12331339 ]
Rick Hillegas commented on DERBY-587:
-
I retract my hasty judgment. I don't think this submission is ready to be
committed. The good news is that the trunk compiles without
[ http://issues.apache.org/jira/browse/DERBY-602?page=all ]
Rick Hillegas resolved DERBY-602:
-
Resolution: Fixed
This is expected behavior. USER is a builtin system function which returns the
authorization id of the current user. Please see the "Bu
[
http://issues.apache.org/jira/browse/DERBY-554?page=comments#action_12331448 ]
Rick Hillegas commented on DERBY-554:
-
This should be fixed when we re-enable the national character string types:
NCHAR and NVARCHAR.
> ORDER By clause doesn't work with
[ http://issues.apache.org/jira/browse/DERBY-516?page=all ]
Rick Hillegas updated DERBY-516:
Attachment: bug516.diff
This patch introduces a small JUnit test for checking the compatibility of
clients
and servers running at different rev levels and on di
[
http://issues.apache.org/jira/browse/DERBY-587?page=comments#action_12331629 ]
Rick Hillegas commented on DERBY-587:
-
Dan raises an uncomfortable issue which I hope we don't have to address for
this submission but which we do have to address for the 1
Make scan Qualifiers smart enough to handle comparisons between columns in the
same row
---
Key: DERBY-619
URL: http://issues.apache.org/jira/browse/DERBY-619
Project: Derby
Type: Im
[ http://issues.apache.org/jira/browse/DERBY-607?page=all ]
Rick Hillegas resolved DERBY-607:
-
Resolution: Fixed
This is because the arguments to procedures are data values (in this case
Strings) rather than SQL identifiers. In SQL-speak, they beha
[ http://issues.apache.org/jira/browse/DERBY-439?page=all ]
Rick Hillegas closed DERBY-439:
---
Resolution: Fixed
Closed by fix to 353.
> IDENTITY_VAL_LOCAL() returns null after INSERT INTO table VALUES(DEFAULT)
> ---
[
http://issues.apache.org/jira/browse/DERBY-516?page=comments#action_12332013 ]
Rick Hillegas commented on DERBY-516:
-
Thanks, David, for reviewing this patch so thoroughly. Based on your review, I
will make several changes and resubmit this patch. Her
[ http://issues.apache.org/jira/browse/DERBY-621?page=all ]
Rick Hillegas closed DERBY-621:
---
Resolution: Fixed
Closed per reporter's judgment.
> PreparedStatement batching does not seem to work with BLOB
>
[
http://issues.apache.org/jira/browse/DERBY-621?page=comments#action_12332411 ]
Rick Hillegas commented on DERBY-621:
-
Sunitha points out that an email discussion linked this issue to bug 621, which
was closed in July.
> PreparedStatement batching doe
[
http://issues.apache.org/jira/browse/DERBY-621?page=comments#action_12332412 ]
Rick Hillegas commented on DERBY-621:
-
Er...make that bug 217, closed in July. Apologies for the JIRA chatter.
> PreparedStatement batching does not seem to work with BLOB
[ http://issues.apache.org/jira/browse/DERBY-516?page=all ]
Rick Hillegas updated DERBY-516:
Attachment: (was: bug516.diff)
> Need to incorporate client backward/forward compatibility testing into
> testing procedures.
> ---
[ http://issues.apache.org/jira/browse/DERBY-516?page=all ]
Rick Hillegas updated DERBY-516:
Attachment: bug516.diff
Hi, David: I have amended this patch as you suggested. I ran derbyall and one
test failed: dataSourcePermissions_net. When I ran derbyne
[
http://issues.apache.org/jira/browse/DERBY-516?page=comments#action_12332533 ]
Rick Hillegas commented on DERBY-516:
-
This patch was scraped from a subversion client at revision 325900.
> Need to incorporate client backward/forward compatibility test
[
http://issues.apache.org/jira/browse/DERBY-634?page=comments#action_12332711 ]
Rick Hillegas commented on DERBY-634:
-
Satheesh adds this explanation:
Thanks Jeff, great analysis... It seems to me it was originally intended
to cache a small number of s
[ http://issues.apache.org/jira/browse/DERBY-516?page=all ]
Rick Hillegas updated DERBY-516:
Attachment: (was: bug516.diff)
> Need to incorporate client backward/forward compatibility testing into
> testing procedures.
> ---
[ http://issues.apache.org/jira/browse/DERBY-516?page=all ]
Rick Hillegas updated DERBY-516:
Attachment: bug516.diff
Incorporate Andrew's suggestion:
1) Amended BUILDING.txt and README.htm.
2) Moved junit jar symbol from compilepath to extrapath and ad
[
http://issues.apache.org/jira/browse/DERBY-472?page=comments#action_12355899 ]
Rick Hillegas commented on DERBY-472:
-
The following wiki page tracks this evolving proposal:
http://wiki.apache.org/db-derby/LuceneIntegration.
> Full Text Indexing / Ful
[
http://issues.apache.org/jira/browse/DERBY-472?page=comments#action_12355900 ]
Rick Hillegas commented on DERBY-472:
-
The following wiki page tracks this evolving proposal:
http://wiki.apache.org/db-derby/LuceneIntegration.
> Full Text Indexing / Ful
[ http://issues.apache.org/jira/browse/DERBY-472?page=all ]
Rick Hillegas updated DERBY-472:
Comment: was deleted
> Full Text Indexing / Full Text Search
> -
>
> Key: DERBY-472
> URL: http://issues.ap
[ http://issues.apache.org/jira/browse/DERBY-516?page=all ]
Rick Hillegas updated DERBY-516:
Attachment: (was: bug516.diff)
> Need to incorporate client backward/forward compatibility testing into
> testing procedures.
> ---
[ http://issues.apache.org/jira/browse/DERBY-516?page=all ]
Rick Hillegas updated DERBY-516:
Attachment: bug516.diff
Fix .../tests/compatibility/build.xml to use 1.3 compile classpath rather than
generic compile classpath. This should fix the compile pr
Useful indexes not used in UNION ALL
Key: DERBY-649
URL: http://issues.apache.org/jira/browse/DERBY-649
Project: Derby
Type: Bug
Reporter: Rick Hillegas
Frederic Moreau reports
(http://mail-archives.apache.org/mod_mbox/db-d
Re-enable the storing of java objects in the database
-
Key: DERBY-651
URL: http://issues.apache.org/jira/browse/DERBY-651
Project: Derby
Type: Bug
Components: SQL
Reporter: Rick Hillegas
Islay Symonette,
[
http://issues.apache.org/jira/browse/DERBY-464?page=comments#action_12356020 ]
Rick Hillegas commented on DERBY-464:
-
At the risk of yanking on the ball of yarn: I think it would be very useful if
this effort included CREATE/DROP ROLE as well. There's
Allow unique constraints to pass if one of the columns is null
--
Key: DERBY-653
URL: http://issues.apache.org/jira/browse/DERBY-653
Project: Derby
Type: Bug
Components: SQL
Reporter: Rick Hillegas
[ http://issues.apache.org/jira/browse/DERBY-651?page=all ]
Rick Hillegas updated DERBY-651:
type: New Feature (was: Bug)
Thanks, Satheesh. You're right, this is an enhancement.
> Re-enable the storing of java objects in the database
>
[ http://issues.apache.org/jira/browse/DERBY-653?page=all ]
Rick Hillegas closed DERBY-653:
---
Resolution: Invalid
Derby, like DB2, finesses this issue by not allowing nullable columns in unique
constraints.
> Allow unique constraints to pass if one o
[
http://issues.apache.org/jira/browse/DERBY-587?page=comments#action_12356162 ]
Rick Hillegas commented on DERBY-587:
-
The patch looks good. Derby builds cleanly. If you put a pointer to jdk16 into
your ant.properties, Derby again builds cleanly, inclu
[
http://issues.apache.org/jira/browse/DERBY-587?page=comments#action_12356415 ]
Rick Hillegas commented on DERBY-587:
-
Thanks for pointing out these issues, Satheesh. I didn't turn up on the
published list until a couple months after I submitted my ICL
[
http://issues.apache.org/jira/browse/DERBY-587?page=comments#action_12356422 ]
Rick Hillegas commented on DERBY-587:
-
Hi Satheesh: Narayanan has faxed in his ICLA. He's on holiday (Diwali) right
now. Would it be ok to clean up the copyright and tag is
[
http://issues.apache.org/jira/browse/DERBY-85?page=comments#action_12356438 ]
Rick Hillegas commented on DERBY-85:
The patch itself looks good. I'm running derbyall now. The patch, however,
needs to add a regression test case to one of the language te
[
http://issues.apache.org/jira/browse/DERBY-85?page=comments#action_12356444 ]
Rick Hillegas commented on DERBY-85:
Derbyall passed. When a new patch is submitted including a regression test,
I'll just run the appropriate suite.
> NPE when creating a
Re-enable user defined aggregates
-
Key: DERBY-672
URL: http://issues.apache.org/jira/browse/DERBY-672
Project: Derby
Type: New Feature
Reporter: Rick Hillegas
Nicolas Dufour in an email thread titled "functions and list" started
[ http://issues.apache.org/jira/browse/DERBY-280?page=all ]
Rick Hillegas reassigned DERBY-280:
---
Assign To: Rick Hillegas
> Wrong result from select when aliasing to same name as used in group by
> --
Get rid of the NodeFactory
--
Key: DERBY-673
URL: http://issues.apache.org/jira/browse/DERBY-673
Project: Derby
Type: New Feature
Reporter: Rick Hillegas
This piece of code once had a purpose in life. It was one of the double-joints
whi
[
http://issues.apache.org/jira/browse/DERBY-280?page=comments#action_12356646 ]
Rick Hillegas commented on DERBY-280:
-
>From my reading of Part 2 of the ANSI spec, this syntax should be disallowed:
select i, count(*) as i from tt group by i;
This quer
[
http://issues.apache.org/jira/browse/DERBY-280?page=comments#action_12356658 ]
Rick Hillegas commented on DERBY-280:
-
Hm, I'm afraid these illegal relations (relations with identically named
columns) turn up everywhere. Disallowing them is not going t
Eliminate the parser's rewriting of the abstract syntax tree for queries with
GROUP BY and/or HAVING clauses
Key: DERBY-681
URL: http://issues.apache.org/jira/browse/DERB
[ http://issues.apache.org/jira/browse/DERBY-280?page=all ]
Rick Hillegas updated DERBY-280:
Attachment: bug280.diff
I am attaching a patch which makes the situation better. I tried a couple
approaches to fixing this bug: 1) I tried fabricating unique a
Various improvements to compatibility test.
---
Key: DERBY-689
URL: http://issues.apache.org/jira/browse/DERBY-689
Project: Derby
Type: Improvement
Reporter: Rick Hillegas
Improve compatibility test as various reviewers r
[ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
Rick Hillegas reassigned DERBY-689:
---
Assign To: Rick Hillegas
> Various improvements to compatibility test.
> ---
>
> Key: DERBY-689
>
[ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
Rick Hillegas updated DERBY-689:
Attachment: bug689.diff
Various improvements to compatibility test:
1) Moved all JUnit tests under a ...functionTests/tests/junitTests as Myrna and
John reques
[
http://issues.apache.org/jira/browse/DERBY-396?page=comments#action_12357085 ]
Rick Hillegas commented on DERBY-396:
-
I think that the Oracle/Postgres RENAME syntax is straightforward and good
enough. Its similarity to Derby's RENAME TABLE syntax is a
[
http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12357094 ]
Rick Hillegas commented on DERBY-289:
-
o Yes, please. Please move SQLState.java to common.
o CommonFeatures doesn't seem to provide much value. Could it be merged into
Sha
[
http://issues.apache.org/jira/browse/DERBY-688?page=comments#action_12357097 ]
Rick Hillegas commented on DERBY-688:
-
Good spec. I have some initial comments on the Usability section:
The spec needs to be enriched by familiarity with JDBC 4.0, which i
Re-enable the TINYINT datatype
--
Key: DERBY-695
URL: http://issues.apache.org/jira/browse/DERBY-695
Project: Derby
Type: New Feature
Reporter: Rick Hillegas
I would like to collect here the arguments for and against re-enabling the
[
http://issues.apache.org/jira/browse/DERBY-695?page=comments#action_12357165 ]
Rick Hillegas commented on DERBY-695:
-
I'm sorry for garbling your argument. I share your feeling that where ANSI does
propose solutions, we should consider them carefully.
[
http://issues.apache.org/jira/browse/DERBY-280?page=comments#action_12357313 ]
Rick Hillegas commented on DERBY-280:
-
It is true that, given this patch, that edge case will raise an error. The
query would have to be rewritten as the error message indi
[
http://issues.apache.org/jira/browse/DERBY-587?page=comments#action_12357595 ]
Rick Hillegas commented on DERBY-587:
-
I have successfully built this patch under jdk1.4 and jdk1.6. For me derbyall
runs cleanly under jdk1.4. Under jdk1.6 the new jdbc4 t
[ http://issues.apache.org/jira/browse/DERBY-689?page=all ]
Rick Hillegas updated DERBY-689:
Attachment: bug689_2.diff
bug689_2.diff further improves this suite by adding a target for running just
one combination of client/clientVM/server/serverVM. The
[ http://issues.apache.org/jira/browse/DERBY-556?page=all ]
Rick Hillegas reassigned DERBY-556:
---
Assign To: Rick Hillegas
> NetworkServer does not set thread context classloader
> -
>
> Key:
[ http://issues.apache.org/jira/browse/DERBY-556?page=all ]
Rick Hillegas updated DERBY-556:
Attachment: MathUtils.jar
z.sql
zz.sql
Hi Jeremy,
Can you explain the problem in greater detail? I successfully did the followin
[ http://issues.apache.org/jira/browse/DERBY-280?page=all ]
Rick Hillegas updated DERBY-280:
Attachment: (was: bug280.diff)
> Wrong result from select when aliasing to same name as used in group by
> --
[ http://issues.apache.org/jira/browse/DERBY-280?page=all ]
Rick Hillegas updated DERBY-280:
Attachment: bug280.diff
I have reapplied this patch to a current snapshot of the mainline. I ran
derbyall. Two tests failed (dataSourcePermissions_net and
Conc
[
http://issues.apache.org/jira/browse/DERBY-85?page=comments#action_12357794 ]
Rick Hillegas commented on DERBY-85:
I don't think I understand the June 21 question about which schema descriptor
method to call. DDLConstantAction.getSchemaDescriptorForCr
[ http://issues.apache.org/jira/browse/DERBY-280?page=all ]
Rick Hillegas updated DERBY-280:
Attachment: (was: bug280.diff)
> Wrong result from select when aliasing to same name as used in group by
> --
[ http://issues.apache.org/jira/browse/DERBY-280?page=all ]
Rick Hillegas updated DERBY-280:
Attachment: bug280.diff
Hi Satheesh,
Thanks for finding this howler. I have fixed the npe and added some more test
cases to verify that fact. Derbyall runs cle
[ http://issues.apache.org/jira/browse/DERBY-556?page=all ]
Rick Hillegas updated DERBY-556:
Attachment: ServerStarter.java
I'm afraid I'm still not getting it. I am able to start the server from a
thread which sets its context class loader to an URLCla
Re-enable VTIs
--
Key: DERBY-716
URL: http://issues.apache.org/jira/browse/DERBY-716
Project: Derby
Type: New Feature
Reporter: Rick Hillegas
Cloudscape used to expose Virtual Table Interfaces, by which any class which
implemented ResultSet could b
[
http://issues.apache.org/jira/browse/DERBY-716?page=comments#action_12357981 ]
Rick Hillegas commented on DERBY-716:
-
This feature is supported by other databases, including DB2 (see
http://publib.boulder.ibm.com/infocenter/db2help/index.jsp?topic=/co
[ http://issues.apache.org/jira/browse/DERBY-556?page=all ]
Rick Hillegas updated DERBY-556:
Attachment: Derby556Tweaked.java
Hi Jeremy,
Thanks for attaching a test case. To run this test case I had to make a couple
changes, which I have attached as De
[ http://issues.apache.org/jira/browse/DERBY-499?page=all ]
Rick Hillegas updated DERBY-499:
Attachment: BooleanFS.html
I have attached a thin functional specification describing expected SQL and
JDBC behavior for the re-enabled BOOLEAN datatype.
> Exp
[ http://issues.apache.org/jira/browse/DERBY-587?page=all ]
Rick Hillegas updated DERBY-587:
Attachment: bug587_javadoc.diff
The original patch broke javadoc generation because the 1.4 javadoc machinery
doesn't understand the 1.6 signatures which contai
[
http://issues.apache.org/jira/browse/DERBY-673?page=comments#action_12358703 ]
Rick Hillegas commented on DERBY-673:
-
This change should not preclude and I expect it would facilitate
reorganizations of the type hierarchy for nodes in the abstract synt
[
http://issues.apache.org/jira/browse/DERBY-673?page=comments#action_12358707 ]
Rick Hillegas commented on DERBY-673:
-
TableName doesn't have a useful optimize() or generate() method but it does
have a bind() method. It looks like a reasonable AST node
[ http://issues.apache.org/jira/browse/DERBY-280?page=all ]
Rick Hillegas resolved DERBY-280:
-
Resolution: Incomplete
I am resolving this bug as Incomplete. The complete fix to this bug is part of
the cleanup described in jira 681.
> Wrong result
[ http://issues.apache.org/jira/browse/DERBY-280?page=all ]
Rick Hillegas closed DERBY-280:
---
The regression test for this patch (in aggregate.sql) succeeds. So I am closing
this bug.
> Wrong result from select when aliasing to same name as used in group
1 - 100 of 8698 matches
Mail list logo
