[jira] Commented: (DERBY-2374) UNION PROBLEM WITH PARENTHESIS

[ https://issues.apache.org/jira/browse/DERBY-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12990938#comment-12990938 ] Lukas Eder commented on DERBY-2374: --- Thanks for all the detailed analyses. This would be

[jira] Issue Comment Edited: (DERBY-2374) UNION PROBLEM WITH PARENTHESIS

[ https://issues.apache.org/jira/browse/DERBY-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12990938#comment-12990938 ] Lukas Eder edited comment on DERBY-2374 at 2/5/11 8:41 AM: ---

[jira] Created: (DERBY-5005) Error when fully qualifying a field from a view in an ORDER BY clause

Error when fully qualifying a field from a view in an ORDER BY clause - Key: DERBY-5005 URL: https://issues.apache.org/jira/browse/DERBY-5005 Project: Derby Issue Type: Bug

[jira] Updated: (DERBY-5005) Error when fully qualifying a field from a view in an ORDER BY clause

[ https://issues.apache.org/jira/browse/DERBY-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Eder updated DERBY-5005: -- Description: I have a strange issue that can be reproduced easily with the following objects in

[jira] Created: (DERBY-5006) Handle NULL literals like any other database

Handle NULL literals like any other database Key: DERBY-5006 URL: https://issues.apache.org/jira/browse/DERBY-5006 Project: Derby Issue Type: Improvement Components: SQL Affects

[jira] Commented: (DERBY-5006) Handle NULL literals like any other database

[ https://issues.apache.org/jira/browse/DERBY-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12991400#comment-12991400 ] Lukas Eder commented on DERBY-5006: --- Hi Rick! Thanks for your feedback. I'm happy if I

[jira] Commented: (DERBY-5006) Handle NULL literals like any other database

[ https://issues.apache.org/jira/browse/DERBY-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12991490#comment-12991490 ] Lukas Eder commented on DERBY-5006: --- Thanks for the insight! I am sure that SQL is a

[jira] Commented: (DERBY-5005) Error when fully qualifying a field from a view in an ORDER BY clause

[ https://issues.apache.org/jira/browse/DERBY-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12992506#comment-12992506 ] Lukas Eder commented on DERBY-5005: --- Excellent guys! That was really quick! :-) Error

[jira] Commented: (DERBY-5005) Error when fully qualifying a field from a view in an ORDER BY clause

[ https://issues.apache.org/jira/browse/DERBY-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12994245#comment-12994245 ] Lukas Eder commented on DERBY-5005: --- Should I verify the correctness of the fix before

[jira] Created: (DERBY-5130) Allow for LONG VARCHAR to be compared to LONG VARCHAR

Allow for LONG VARCHAR to be compared to LONG VARCHAR - Key: DERBY-5130 URL: https://issues.apache.org/jira/browse/DERBY-5130 Project: Derby Issue Type: Improvement Components:

[jira] Commented: (DERBY-5130) Allow for LONG VARCHAR to be compared to LONG VARCHAR

[ https://issues.apache.org/jira/browse/DERBY-5130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13007057#comment-13007057 ] Lukas Eder commented on DERBY-5130: --- Hmm, you're right. I agree that it is consistent

[jira] [Commented] (DERBY-4379) Let´s add comments to Derby

[ https://issues.apache.org/jira/browse/DERBY-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13011803#comment-13011803 ] Lukas Eder commented on DERBY-4379: --- I am missing this feature as well. Many databases

[jira] [Created] (DERBY-5214) Make DATETIME arithmetic functions easier to use

Make DATETIME arithmetic functions easier to use Key: DERBY-5214 URL: https://issues.apache.org/jira/browse/DERBY-5214 Project: Derby Issue Type: Improvement Components: JDBC, SQL

[jira] [Commented] (DERBY-3893) Implement two-argument functions POWER, ROUND, and TRUNCATE

[ https://issues.apache.org/jira/browse/DERBY-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028205#comment-13028205 ] Lukas Eder commented on DERBY-3893: --- I think so too, this would be very useful

[jira] [Created] (DERBY-5216) Add support for GREATEST and LEAST functions

Add support for GREATEST and LEAST functions Key: DERBY-5216 URL: https://issues.apache.org/jira/browse/DERBY-5216 Project: Derby Issue Type: Improvement Components: SQL Affects

[jira] [Commented] (DERBY-5005) Error when fully qualifying a field from a view in an ORDER BY clause

[ https://issues.apache.org/jira/browse/DERBY-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13033611#comment-13033611 ] Lukas Eder commented on DERBY-5005: --- Works for me in 10.8. Thanks guys Error when

[jira] [Closed] (DERBY-5005) Error when fully qualifying a field from a view in an ORDER BY clause

[ https://issues.apache.org/jira/browse/DERBY-5005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Eder closed DERBY-5005. - Error when fully qualifying a field from a view in an ORDER BY clause

[jira] [Created] (DERBY-5320) Support for RPAD, LPAD, REPEAT string functions

Support for RPAD, LPAD, REPEAT string functions --- Key: DERBY-5320 URL: https://issues.apache.org/jira/browse/DERBY-5320 Project: Derby Issue Type: Improvement Components: SQL

[jira] [Created] (DERBY-5837) Add support for SQL standard DATE, TIME, TIMESTAMP literals

Lukas Eder created DERBY-5837: - Summary: Add support for SQL standard DATE, TIME, TIMESTAMP literals Key: DERBY-5837 URL: https://issues.apache.org/jira/browse/DERBY-5837 Project: Derby Issue

[jira] [Created] (DERBY-5893) Add support for the SQL:2008 standard IS [ NOT ] DISTINCT FROM predicate

Lukas Eder created DERBY-5893: - Summary: Add support for the SQL:2008 standard IS [ NOT ] DISTINCT FROM predicate Key: DERBY-5893 URL: https://issues.apache.org/jira/browse/DERBY-5893 Project: Derby

[jira] [Comment Edited] (DERBY-5893) Add support for the SQL:2008 standard IS [ NOT ] DISTINCT FROM predicate

[ https://issues.apache.org/jira/browse/DERBY-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428647#comment-13428647 ] Lukas Eder edited comment on DERBY-5893 at 8/4/12 5:39 PM: --- Yes,

[jira] [Comment Edited] (DERBY-5893) Add support for the SQL:2008 standard IS [ NOT ] DISTINCT FROM predicate

[ https://issues.apache.org/jira/browse/DERBY-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428647#comment-13428647 ] Lukas Eder edited comment on DERBY-5893 at 8/4/12 5:39 PM: --- Yes,

[jira] [Commented] (DERBY-5893) Add support for the SQL:2008 standard IS [ NOT ] DISTINCT FROM predicate

[ https://issues.apache.org/jira/browse/DERBY-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428647#comment-13428647 ] Lukas Eder commented on DERBY-5893: --- Yes, it's different in the way it handles NULLs.

[jira] [Created] (DERBY-6228) DisconnectException when executing an SELECT [LOB column] ORDER BY [...] statement with TYPE_SCROLL_[IN]SENSITIVE and CONCUR_UPDATABLE

Lukas Eder created DERBY-6228: - Summary: DisconnectException when executing an SELECT [LOB column] ORDER BY [...] statement with TYPE_SCROLL_[IN]SENSITIVE and CONCUR_UPDATABLE Key: DERBY-6228 URL:

[jira] [Commented] (DERBY-4138) Adding an ORDER BY clause breaks updatable result sets

[ https://issues.apache.org/jira/browse/DERBY-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666467#comment-13666467 ] Lukas Eder commented on DERBY-4138: --- See also DERBY-6228, where adding an ORDER BY

[jira] [Created] (DERBY-6444) Add support for INSERT INTO table DEFAULT VALUES syntax

Lukas Eder created DERBY-6444: - Summary: Add support for INSERT INTO table DEFAULT VALUES syntax Key: DERBY-6444 URL: https://issues.apache.org/jira/browse/DERBY-6444 Project: Derby Issue Type:

[jira] [Commented] (DERBY-896) Cast date to timestamp results in ERROR 42846: Cannot convert types 'DATE' to 'TIMESTAMP'.

[ https://issues.apache.org/jira/browse/DERBY-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13899283#comment-13899283 ] Lukas Eder commented on DERBY-896: -- I can reproduce this issue with {code} select

[jira] [Commented] (DERBY-896) Cast date to timestamp results in ERROR 42846: Cannot convert types 'DATE' to 'TIMESTAMP'.

[ https://issues.apache.org/jira/browse/DERBY-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13903113#comment-13903113 ] Lukas Eder commented on DERBY-896: -- That is great, thank you very much, guys! Cast date

[jira] [Created] (DERBY-6489) Add support for the SQL Standard ALTER SEQUENCE statement

Lukas Eder created DERBY-6489: - Summary: Add support for the SQL Standard ALTER SEQUENCE statement Key: DERBY-6489 URL: https://issues.apache.org/jira/browse/DERBY-6489 Project: Derby Issue

[jira] [Comment Edited] (DERBY-1576) Extend the CASE expression syntax for simple case

[ https://issues.apache.org/jira/browse/DERBY-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985333#comment-13985333 ] Lukas Eder edited comment on DERBY-1576 at 4/30/14 9:48 AM:

[jira] [Commented] (DERBY-1576) Extend the CASE expression syntax for simple case

[ https://issues.apache.org/jira/browse/DERBY-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985333#comment-13985333 ] Lukas Eder commented on DERBY-1576: --- Hmm, apart from MS Access (which doesn't have a

[jira] [Commented] (DERBY-1576) Extend the CASE expression syntax for simple case

[ https://issues.apache.org/jira/browse/DERBY-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13985423#comment-13985423 ] Lukas Eder commented on DERBY-1576: --- Very nice, I wasn't aware of this interpretation of

[jira] [Created] (DERBY-6758) Driver.connect() returns null when using file-based URL

Lukas Eder created DERBY-6758: - Summary: Driver.connect() returns null when using file-based URL Key: DERBY-6758 URL: https://issues.apache.org/jira/browse/DERBY-6758 Project: Derby Issue Type:

[jira] [Created] (DERBY-6757) Driver.connect() returns null when using file-based URL

Lukas Eder created DERBY-6757: - Summary: Driver.connect() returns null when using file-based URL Key: DERBY-6757 URL: https://issues.apache.org/jira/browse/DERBY-6757 Project: Derby Issue Type:

[jira] [Commented] (DERBY-6758) Driver.connect() returns null when using file-based URL

[ https://issues.apache.org/jira/browse/DERBY-6758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14160341#comment-14160341 ] Lukas Eder commented on DERBY-6758: --- Oh man. I just now realised that I wasn't using

[jira] [Closed] (DERBY-6758) Driver.connect() returns null when using file-based URL

[ https://issues.apache.org/jira/browse/DERBY-6758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Eder closed DERBY-6758. - Resolution: Invalid Driver.connect() returns null when using file-based URL

[jira] [Commented] (DERBY-6757) Driver.connect() returns null when using file-based URL

[ https://issues.apache.org/jira/browse/DERBY-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173365#comment-14173365 ] Lukas Eder commented on DERBY-6757: --- Hmm, interesting - I had realised my mistake and I

[jira] [Closed] (DERBY-6757) Driver.connect() returns null when using file-based URL

[ https://issues.apache.org/jira/browse/DERBY-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Eder closed DERBY-6757. - Resolution: Not a Problem Driver.connect() returns null when using file-based URL

[jira] [Commented] (DERBY-6813) Undocumented ON DELETE SET DEFAULT is parsed, accepted, but not enforced

[ https://issues.apache.org/jira/browse/DERBY-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567613#comment-14567613 ] Lukas Eder commented on DERBY-6813: --- [~bryanpendleton]: Thanks for the hints. I'm just

[jira] [Created] (DERBY-6812) Make RESTRICT an optional keyword in DROP SEQUENCE

Lukas Eder created DERBY-6812: - Summary: Make RESTRICT an optional keyword in DROP SEQUENCE Key: DERBY-6812 URL: https://issues.apache.org/jira/browse/DERBY-6812 Project: Derby Issue Type:

[jira] [Created] (DERBY-6813) Undocumented ON DELETE SET DEFAULT is parsed, accepted, but not enforced

Lukas Eder created DERBY-6813: - Summary: Undocumented ON DELETE SET DEFAULT is parsed, accepted, but not enforced Key: DERBY-6813 URL: https://issues.apache.org/jira/browse/DERBY-6813 Project: Derby

[jira] [Created] (DERBY-6952) Regression on Statement.getGeneratedKeys() on UPDATE statements

Lukas Eder created DERBY-6952: - Summary: Regression on Statement.getGeneratedKeys() on UPDATE statements Key: DERBY-6952 URL: https://issues.apache.org/jira/browse/DERBY-6952 Project: Derby

[jira] [Created] (DERBY-6953) Support the SQL Standard

Lukas Eder created DERBY-6953: - Summary: Support the SQL Standard Key: DERBY-6953 URL: https://issues.apache.org/jira/browse/DERBY-6953 Project: Derby Issue Type: Improvement

[jira] [Commented] (DERBY-6952) Regression on Statement.getGeneratedKeys() on UPDATE statements

[ https://issues.apache.org/jira/browse/DERBY-6952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095985#comment-16095985 ] Lukas Eder commented on DERBY-6952: --- Thanks for linking. Of course, the soundest solution that would

[jira] [Updated] (DERBY-6947) Simple query runs forever

[ https://issues.apache.org/jira/browse/DERBY-6947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Eder updated DERBY-6947: -- Description: {code} select X1.A as A1, X2.A as A2 from ( select * from ( select 1 as A

[jira] [Created] (DERBY-6947) Simple query runs forever

Lukas Eder created DERBY-6947: - Summary: Simple query runs forever Key: DERBY-6947 URL: https://issues.apache.org/jira/browse/DERBY-6947 Project: Derby Issue Type: Bug Components: SQL

[jira] [Commented] (DERBY-6948) INSERT .. SELECT produces NULL for getGeneratedKeys()

[ https://issues.apache.org/jira/browse/DERBY-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075961#comment-16075961 ] Lukas Eder commented on DERBY-6948: --- I see, thanks for linking, Rick. Is there any SQL-based workaround

[jira] [Commented] (DERBY-6948) INSERT .. SELECT produces NULL for getGeneratedKeys()

[ https://issues.apache.org/jira/browse/DERBY-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074772#comment-16074772 ] Lukas Eder commented on DERBY-6948: --- >From the description, I wasn't sure if this issue is the same as

[jira] [Created] (DERBY-6948) INSERT .. SELECT produces NULL for getGeneratedKeys()

Lukas Eder created DERBY-6948: - Summary: INSERT .. SELECT produces NULL for getGeneratedKeys() Key: DERBY-6948 URL: https://issues.apache.org/jira/browse/DERBY-6948 Project: Derby Issue Type:

[jira] [Commented] (DERBY-6948) INSERT .. SELECT produces NULL for getGeneratedKeys()

[ https://issues.apache.org/jira/browse/DERBY-6948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16077722#comment-16077722 ] Lukas Eder commented on DERBY-6948: --- I see, thanks [~rhillegas]. Unfortunately, I cannot make that

[jira] [Commented] (DERBY-4842) Support "IF [NOT] EXISTS" in CREATE TABLE and "IF EXISTS" in DROP TABLE

[ https://issues.apache.org/jira/browse/DERBY-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264302#comment-16264302 ] Lukas Eder commented on DERBY-4842: --- This would be really useful. PostgreSQL and MySQL went quite far

[jira] [Commented] (DERBY-4842) Support "IF [NOT] EXISTS" in CREATE TABLE and "IF EXISTS" in DROP TABLE

[ https://issues.apache.org/jira/browse/DERBY-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265485#comment-16265485 ] Lukas Eder commented on DERBY-4842: --- In many years of working with SQL, I have never felt the need of

[jira] [Created] (DERBY-6983) Support SELECT * for IN predicate subqueries when it is "obvious" that the asterisk expands to exactly one column

Lukas Eder created DERBY-6983: - Summary: Support SELECT * for IN predicate subqueries when it is "obvious" that the asterisk expands to exactly one column Key: DERBY-6983 URL:

[jira] [Commented] (DERBY-6983) Support SELECT * for IN predicate subqueries when it is "obvious" that the asterisk expands to exactly one column

[ https://issues.apache.org/jira/browse/DERBY-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377397#comment-16377397 ] Lukas Eder commented on DERBY-6983: --- Thanks for your comment, Rick. I'm well aware of the fact that the

[jira] [Commented] (DERBY-6983) Support SELECT * for IN predicate subqueries when it is "obvious" that the asterisk expands to exactly one column

[ https://issues.apache.org/jira/browse/DERBY-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381758#comment-16381758 ] Lukas Eder commented on DERBY-6983: --- I see, thanks a lot for the clarification. Indeed, it did not occur

[jira] [Created] (DERBY-6984) Cannot use UNION in correlated subquery or derived table when first UNION subquery is parenthesised

Lukas Eder created DERBY-6984: - Summary: Cannot use UNION in correlated subquery or derived table when first UNION subquery is parenthesised Key: DERBY-6984 URL: https://issues.apache.org/jira/browse/DERBY-6984

[jira] [Commented] (DERBY-7009) DECIMAL(33, 3) Type cannot be used in CAST expression, but can appear in views

[ https://issues.apache.org/jira/browse/DERBY-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16633688#comment-16633688 ] Lukas Eder commented on DERBY-7009: --- {quote}Other than being puzzling, can you think of any harm caused

[jira] [Created] (DERBY-7008) Add support for COMMENT ON [ object ] IS '...' statements

Lukas Eder created DERBY-7008: - Summary: Add support for COMMENT ON [ object ] IS '...' statements Key: DERBY-7008 URL: https://issues.apache.org/jira/browse/DERBY-7008 Project: Derby Issue

[jira] [Updated] (DERBY-7009) DECIMAL(33, 3) Type cannot be used in CAST expression, but can appear in views

[ https://issues.apache.org/jira/browse/DERBY-7009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Eder updated DERBY-7009: -- Description: In the manual, there is a claim that the maximum precision for the DECIMAL data type is

[jira] [Created] (DERBY-7009) DECIMAL(33, 3) Type cannot be used in CAST expression, but can appear in views

Lukas Eder created DERBY-7009: - Summary: DECIMAL(33, 3) Type cannot be used in CAST expression, but can appear in views Key: DERBY-7009 URL: https://issues.apache.org/jira/browse/DERBY-7009 Project:

[jira] [Commented] (DERBY-2072) Implement CAST from INTEGER (and other numeric types) to VARCHAR

[ https://issues.apache.org/jira/browse/DERBY-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154473#comment-17154473 ] Lukas Eder commented on DERBY-2072: --- For the record, this can be circumvented by casting to CHAR first:

[jira] [Created] (DERBY-7139) Boolean expressions cannot be passed to COALESCE function

Lukas Eder created DERBY-7139: - Summary: Boolean expressions cannot be passed to COALESCE function Key: DERBY-7139 URL: https://issues.apache.org/jira/browse/DERBY-7139 Project: Derby Issue

[jira] [Created] (DERBY-7146) NullPointerException when executing MERGE statement with NULL value in INSERT clause

Lukas Eder created DERBY-7146: - Summary: NullPointerException when executing MERGE statement with NULL value in INSERT clause Key: DERBY-7146 URL: https://issues.apache.org/jira/browse/DERBY-7146

[jira] [Updated] (DERBY-7146) NullPointerException when executing MERGE statement with NULL value in INSERT clause

[ https://issues.apache.org/jira/browse/DERBY-7146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Eder updated DERBY-7146: -- Description: Try this: {code:sql} create table x ( i int, c varchar(10), primary key (i) );

[jira] [Created] (DERBY-7148) SQL Error [20000] [38000]: The exception 'java.lang.NoSuchMethodError: 'boolean org.apache.derby.iapi.types.DataValueDescriptor.equals(boolean)'' was thrown while evaluat

Lukas Eder created DERBY-7148: - Summary: SQL Error [2] [38000]: The exception 'java.lang.NoSuchMethodError: 'boolean org.apache.derby.iapi.types.DataValueDescriptor.equals(boolean)'' was thrown while evaluating an expression.

[jira] [Commented] (DERBY-7148) SQL Error [20000] [38000]: The exception 'java.lang.NoSuchMethodError: 'boolean org.apache.derby.iapi.types.DataValueDescriptor.equals(boolean)'' was thrown while evalu

[ https://issues.apache.org/jira/browse/DERBY-7148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635335#comment-17635335 ] Lukas Eder commented on DERBY-7148: --- A workaround is to cast the COALESCE expression to BOOLEAN: