[jira] [Updated] (CALCITE-1928) Calling previous() on a ResultSet that came from an Array gives NullPointerException

[ https://issues.apache.org/jira/browse/CALCITE-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated CALCITE-1928: - Fix Version/s: avatica-1.11.0 > Calling previous() on a ResultSet that came from an Array gives

[jira] [Comment Edited] (CALCITE-1902) ResultSet.previous() throws UnsupportedOperationException, but should throw SQLFeatureNotSupportedException

[ https://issues.apache.org/jira/browse/CALCITE-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114971#comment-16114971 ] Julian Hyde edited comment on CALCITE-1902 at 8/4/17 9:11 PM: -- You're

[jira] [Commented] (CALCITE-1902) ResultSet.previous() throws UnsupportedOperationException, but should throw SQLFeatureNotSupportedException

[ https://issues.apache.org/jira/browse/CALCITE-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114971#comment-16114971 ] Julian Hyde commented on CALCITE-1902: -- You're right. My bad. I logged

[jira] [Updated] (CALCITE-1928) Calling previous() on a ResultSet that came from an Array gives NullPointerException

[ https://issues.apache.org/jira/browse/CALCITE-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated CALCITE-1928: - Component/s: avatica > Calling previous() on a ResultSet that came from an Array gives >

[jira] [Created] (CALCITE-1928) Calling previous() on a ResultSet that came from an Array gives NullPointerException

Julian Hyde created CALCITE-1928: Summary: Calling previous() on a ResultSet that came from an Array gives NullPointerException Key: CALCITE-1928 URL: https://issues.apache.org/jira/browse/CALCITE-1928

[jira] [Commented] (CALCITE-1906) JdbcSortRule has a bug and it is never chosen

[ https://issues.apache.org/jira/browse/CALCITE-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114966#comment-16114966 ] Luis Fernando Kauer commented on CALCITE-1906: -- Debugging some more about this problem, I

[jira] [Commented] (CALCITE-1927) Mapping for Types.BIT: boolean or BitSet?

[ https://issues.apache.org/jira/browse/CALCITE-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114944#comment-16114944 ] Julian Hyde commented on CALCITE-1927: -- To keep this simple, remember we're just considering the

[jira] [Commented] (CALCITE-1927) Mapping for Types.BIT: boolean or BitSet?

[ https://issues.apache.org/jira/browse/CALCITE-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114766#comment-16114766 ] Vladimir Sitnikov commented on CALCITE-1927: {quote}If you mean setting the value of a

[jira] [Commented] (CALCITE-1927) Mapping for Types.BIT: boolean or BitSet?

[ https://issues.apache.org/jira/browse/CALCITE-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114748#comment-16114748 ] Julian Hyde commented on CALCITE-1927: -- bq. There's setObject as well, and it would be quite hard

[jira] [Commented] (CALCITE-1927) Mapping for Types.BIT: boolean or BitSet?

[ https://issues.apache.org/jira/browse/CALCITE-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114687#comment-16114687 ] Vladimir Sitnikov commented on CALCITE-1927: {quote}getBoolean should give a value if m <=

[jira] [Commented] (CALCITE-1927) Mapping for Types.BIT: boolean or BitSet?

[ https://issues.apache.org/jira/browse/CALCITE-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114668#comment-16114668 ] Julian Hyde commented on CALCITE-1927: -- So I guess some databases allow only {{BIT(1)}} and others

[jira] [Commented] (CALCITE-1927) Mapping for Types.BIT: boolean or BitSet?

[ https://issues.apache.org/jira/browse/CALCITE-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114633#comment-16114633 ] Julian Hyde commented on CALCITE-1927: -- The BIT type is obsolete in the SQL standard, so I don't

[jira] [Updated] (CALCITE-1927) Mapping for Types.BIT: boolean or BitSet?

[ https://issues.apache.org/jira/browse/CALCITE-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Sitnikov updated CALCITE-1927: --- Description: Currently Avatica implements `Types.BIT` as `Boolean` (see

[jira] [Created] (CALCITE-1927) Mapping for Types.BIT: boolean or BitSet?

Vladimir Sitnikov created CALCITE-1927: -- Summary: Mapping for Types.BIT: boolean or BitSet? Key: CALCITE-1927 URL: https://issues.apache.org/jira/browse/CALCITE-1927 Project: Calcite

[jira] [Commented] (CALCITE-1902) ResultSet.previous() throws UnsupportedOperationException, but should throw SQLFeatureNotSupportedException

[ https://issues.apache.org/jira/browse/CALCITE-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114479#comment-16114479 ] Sergio Sainz commented on CALCITE-1902: --- Hey [~julianhyde], thanks for the review :) I used

[jira] [Created] (CALCITE-1926) Function names are unparsed quoted while PostgreSQL can only handle unquoted function names

Muhammad Gelbana created CALCITE-1926: - Summary: Function names are unparsed quoted while PostgreSQL can only handle unquoted function names Key: CALCITE-1926 URL:

[jira] [Commented] (CALCITE-1925) JaninoRelMetadataProvider to cache null value

[ https://issues.apache.org/jira/browse/CALCITE-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114118#comment-16114118 ] Ted Xu commented on CALCITE-1925: - Here https://github.com/apache/calcite/pull/507 is a rough showcase.

[jira] [Created] (CALCITE-1925) JaninoRelMetadataProvider to cache null value

Ted Xu created CALCITE-1925: --- Summary: JaninoRelMetadataProvider to cache null value Key: CALCITE-1925 URL: https://issues.apache.org/jira/browse/CALCITE-1925 Project: Calcite Issue Type: