[jira] [Updated] (DERBY-7041) null pointer exception when creating view based on other views
[
https://issues.apache.org/jira/browse/DERBY-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-7041:
-
Attachment: derby-7041-01-aa-omitDependencyOnSystemSuppliedAggregate.diff
> null pointer exception when creating view based on other views
> --
>
> Key: DERBY-7041
> URL: https://issues.apache.org/jira/browse/DERBY-7041
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.14.2.0
> Environment: max os x , intellij
>Reporter: Manuel Rossetti
>Priority: Major
> Attachments: JSLDb.sql, JSLDb.sql, JSLDb_DriveThroughPharmacy.zip,
> derby-7041-01-aa-omitDependencyOnSystemSuppliedAggregate.diff, derby-7041.sql
>
>
> I can execute a SELECT query that works but when I try to create a view on
> that select query, I simply get a java null pointer exception with no
> details. I have tested the same statements on a postgres database and they
> worked without error.
> Below, the PW_DIFF_WITHIN_REP_VIEW create does work, but the
> PW_DIFF_AR_REP_VIEW does not. Again, the SELECT clause of
> PW_DIFF_AR_REP_VIEW will work, but when used within the create clause the
> error occurs.
> I have attached the entire database creation script and an embedded instance
> that can be used for testing. It has data.
>
> -- WITHIN_REP_VIEW combines the WITHIN_REP_COUNTER_VIEW and
> WITHIN_REP_RESPONSE_VIEW into one table from which across
> -- replication or other statistical summaries by replication can be produced
> CREATE VIEW JSL_DB.WITHIN_REP_VIEW (SIM_RUN_ID_FK, EXP_NAME, ELEMENT_NAME,
> STAT_NAME, REP_NUM, VALUE) AS
> (SELECT JSL_DB.WITHIN_REP_STAT.SIM_RUN_ID_FK, EXP_NAME, ELEMENT_NAME,
> STAT_NAME, REP_NUM, AVERAGE AS VALUE
> FROM (JSL_DB.SIMULATION_RUN JOIN JSL_DB.WITHIN_REP_STAT on
> JSL_DB.SIMULATION_RUN.ID = JSL_DB.WITHIN_REP_STAT.SIM_RUN_ID_FK)
> JOIN JSL_DB.MODEL_ELEMENT ON ELEMENT_ID =
> JSL_DB.WITHIN_REP_STAT.ELEMENT_ID_FK
> UNION
> SELECT JSL_DB.WITHIN_REP_COUNTER_STAT.SIM_RUN_ID_FK, EXP_NAME, ELEMENT_NAME,
> STAT_NAME, REP_NUM, LAST_VALUE as VALUE
> FROM (JSL_DB.SIMULATION_RUN JOIN JSL_DB.WITHIN_REP_COUNTER_STAT on
> JSL_DB.SIMULATION_RUN.ID = JSL_DB.WITHIN_REP_COUNTER_STAT.SIM_RUN_ID_FK)
> JOIN JSL_DB.MODEL_ELEMENT ON ELEMENT_ID =
> JSL_DB.WITHIN_REP_COUNTER_STAT.ELEMENT_ID_FK);
>
> -- PW_DIFF_WITHIN_REP_VIEW computes the pairwise differences across
> difference simulation experiments
> -- doesn't work for derby, 3-28-2019, works for postgres
> --
> -- create view JSL_DB.PW_DIFF_WITHIN_REP_VIEW
> -- as (select SIMULATION_RUN.SIM_NAME, A.SIM_RUN_ID_FK AS A_SIM_NUM,
> A.STAT_NAME, A.EXP_NAME as A_EXP_NAME, A.REP_NUM, A.VALUE as A_VALUE,
> -- B.SIM_RUN_ID_FK as B_SIM_NUM, B.EXP_NAME as B_EXP_NAME, B.VALUE as B_VALUE,
> -- '(' || A.EXP_NAME || ' - ' || B.EXP_NAME || ')' as DIFF_NAME, (A.VALUE -
> B.VALUE) as A_MINUS_B
> -- from JSL_DB.WITHIN_REP_VIEW as A, JSL_DB.WITHIN_REP_VIEW as B,
> JSL_DB.SIMULATION_RUN
> -- where A.SIM_RUN_ID_FK = JSL_DB.SIMULATION_RUN.ID
> -- and A.STAT_NAME = B.STAT_NAME
> -- and A.REP_NUM = B.REP_NUM
> -- and A.SIM_RUN_ID_FK > B.SIM_RUN_ID_FK
> -- and A.ELEMENT_NAME = B.ELEMENT_NAME);
> --
> -- create view JSL_DB.PW_DIFF_AR_REP_VIEW (SIM_NAME, STAT_NAME, A_EXP_NAME,
> B_EXP_NAME, DIFF_NAME, AVG_A, STD_DEV_A,
> -- AVG_B, STD_DEV_B, AVG_DIFF_A_MINUS_B, STD_DEV_DIFF_A_MINUS_B, STAT_COUNT)
> -- as (select SIM_NAME, STAT_NAME, A_EXP_NAME, B_EXP_NAME, DIFF_NAME,
> AVG(A_VALUE) as AVG_A, STDDEV_SAMP(A_VALUE) as STD_DEV_A,
> -- AVG(B_VALUE) as AVG_B, STDDEV_SAMP(B_VALUE) as STD_DEV_B,
> -- AVG(A_MINUS_B) as AVG_DIFF_A_MINUS_B, STDDEV_SAMP(A_MINUS_B) as
> STD_DEV_DIFF_A_MINUS_B,
> -- COUNT(A_MINUS_B) as STAT_COUNT
> -- from JSL_DB.PW_DIFF_WITHIN_REP_VIEW
> -- group by SIM_NAME, STAT_NAME, A_EXP_NAME, B_EXP_NAME, DIFF_NAME);
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DERBY-7041) null pointer exception when creating view based on other views
[
https://issues.apache.org/jira/browse/DERBY-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806302#comment-16806302
]
Rick Hillegas commented on DERBY-7041:
--
Attaching derby-7041-01-aa-omitDependencyOnSystemSuppliedAggregate.diff. This
patch makes view creation skip dependency registration between views and
system-supplied aggregates.
I will run the full test suite.
Touches the following files:
{noformat}
---
M
java/org.apache.derby.engine/org/apache/derby/impl/sql/compile/AggregateNode.java
Don't create a persistent dependency from a view to a user-defined
aggregate which is really a system-supplied aggregate implemented via
the user-defined aggregate machinery.
---
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/AggBuiltinTest.java
Add a test case verifying that the NPE has disappeared.
{noformat}
> null pointer exception when creating view based on other views
> --
>
> Key: DERBY-7041
> URL: https://issues.apache.org/jira/browse/DERBY-7041
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.14.2.0
> Environment: max os x , intellij
>Reporter: Manuel Rossetti
>Priority: Major
> Attachments: JSLDb.sql, JSLDb.sql, JSLDb_DriveThroughPharmacy.zip,
> derby-7041-01-aa-omitDependencyOnSystemSuppliedAggregate.diff, derby-7041.sql
>
>
> I can execute a SELECT query that works but when I try to create a view on
> that select query, I simply get a java null pointer exception with no
> details. I have tested the same statements on a postgres database and they
> worked without error.
> Below, the PW_DIFF_WITHIN_REP_VIEW create does work, but the
> PW_DIFF_AR_REP_VIEW does not. Again, the SELECT clause of
> PW_DIFF_AR_REP_VIEW will work, but when used within the create clause the
> error occurs.
> I have attached the entire database creation script and an embedded instance
> that can be used for testing. It has data.
>
> -- WITHIN_REP_VIEW combines the WITHIN_REP_COUNTER_VIEW and
> WITHIN_REP_RESPONSE_VIEW into one table from which across
> -- replication or other statistical summaries by replication can be produced
> CREATE VIEW JSL_DB.WITHIN_REP_VIEW (SIM_RUN_ID_FK, EXP_NAME, ELEMENT_NAME,
> STAT_NAME, REP_NUM, VALUE) AS
> (SELECT JSL_DB.WITHIN_REP_STAT.SIM_RUN_ID_FK, EXP_NAME, ELEMENT_NAME,
> STAT_NAME, REP_NUM, AVERAGE AS VALUE
> FROM (JSL_DB.SIMULATION_RUN JOIN JSL_DB.WITHIN_REP_STAT on
> JSL_DB.SIMULATION_RUN.ID = JSL_DB.WITHIN_REP_STAT.SIM_RUN_ID_FK)
> JOIN JSL_DB.MODEL_ELEMENT ON ELEMENT_ID =
> JSL_DB.WITHIN_REP_STAT.ELEMENT_ID_FK
> UNION
> SELECT JSL_DB.WITHIN_REP_COUNTER_STAT.SIM_RUN_ID_FK, EXP_NAME, ELEMENT_NAME,
> STAT_NAME, REP_NUM, LAST_VALUE as VALUE
> FROM (JSL_DB.SIMULATION_RUN JOIN JSL_DB.WITHIN_REP_COUNTER_STAT on
> JSL_DB.SIMULATION_RUN.ID = JSL_DB.WITHIN_REP_COUNTER_STAT.SIM_RUN_ID_FK)
> JOIN JSL_DB.MODEL_ELEMENT ON ELEMENT_ID =
> JSL_DB.WITHIN_REP_COUNTER_STAT.ELEMENT_ID_FK);
>
> -- PW_DIFF_WITHIN_REP_VIEW computes the pairwise differences across
> difference simulation experiments
> -- doesn't work for derby, 3-28-2019, works for postgres
> --
> -- create view JSL_DB.PW_DIFF_WITHIN_REP_VIEW
> -- as (select SIMULATION_RUN.SIM_NAME, A.SIM_RUN_ID_FK AS A_SIM_NUM,
> A.STAT_NAME, A.EXP_NAME as A_EXP_NAME, A.REP_NUM, A.VALUE as A_VALUE,
> -- B.SIM_RUN_ID_FK as B_SIM_NUM, B.EXP_NAME as B_EXP_NAME, B.VALUE as B_VALUE,
> -- '(' || A.EXP_NAME || ' - ' || B.EXP_NAME || ')' as DIFF_NAME, (A.VALUE -
> B.VALUE) as A_MINUS_B
> -- from JSL_DB.WITHIN_REP_VIEW as A, JSL_DB.WITHIN_REP_VIEW as B,
> JSL_DB.SIMULATION_RUN
> -- where A.SIM_RUN_ID_FK = JSL_DB.SIMULATION_RUN.ID
> -- and A.STAT_NAME = B.STAT_NAME
> -- and A.REP_NUM = B.REP_NUM
> -- and A.SIM_RUN_ID_FK > B.SIM_RUN_ID_FK
> -- and A.ELEMENT_NAME = B.ELEMENT_NAME);
> --
> -- create view JSL_DB.PW_DIFF_AR_REP_VIEW (SIM_NAME, STAT_NAME, A_EXP_NAME,
> B_EXP_NAME, DIFF_NAME, AVG_A, STD_DEV_A,
> -- AVG_B, STD_DEV_B, AVG_DIFF_A_MINUS_B, STD_DEV_DIFF_A_MINUS_B, STAT_COUNT)
> -- as (select SIM_NAME, STAT_NAME, A_EXP_NAME, B_EXP_NAME, DIFF_NAME,
> AVG(A_VALUE) as AVG_A, STDDEV_SAMP(A_VALUE) as STD_DEV_A,
> -- AVG(B_VALUE) as AVG_B, STDDEV_SAMP(B_VALUE) as STD_DEV_B,
> -- AVG(A_MINUS_B) as AVG_DIFF_A_MINUS_B, STDDEV_SAMP(A_MINUS_B) as
> STD_DEV_DIFF_A_MINUS_B,
> -- COUNT(A_MINUS_B) as STAT_COUNT
> -- from JSL_DB.PW_DIFF_WITHIN_REP_VIEW
> -- group by SIM_NAME, STAT_NAME, A_EXP_NAME, B_EXP_NAME, DIFF_NAME);
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DERBY-7041) null pointer exception when creating view based on other views
[
https://issues.apache.org/jira/browse/DERBY-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806301#comment-16806301
]
Rick Hillegas commented on DERBY-7041:
--
No NPE occurs when I substitute a user-defined aggregate for the STDDEV_SAMP.
So the object ID is disappearing only for the statistical aggregates as far as
I can see.
> null pointer exception when creating view based on other views
> --
>
> Key: DERBY-7041
> URL: https://issues.apache.org/jira/browse/DERBY-7041
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.14.2.0
> Environment: max os x , intellij
>Reporter: Manuel Rossetti
>Priority: Major
> Attachments: JSLDb.sql, JSLDb.sql, JSLDb_DriveThroughPharmacy.zip,
> derby-7041.sql
>
>
> I can execute a SELECT query that works but when I try to create a view on
> that select query, I simply get a java null pointer exception with no
> details. I have tested the same statements on a postgres database and they
> worked without error.
> Below, the PW_DIFF_WITHIN_REP_VIEW create does work, but the
> PW_DIFF_AR_REP_VIEW does not. Again, the SELECT clause of
> PW_DIFF_AR_REP_VIEW will work, but when used within the create clause the
> error occurs.
> I have attached the entire database creation script and an embedded instance
> that can be used for testing. It has data.
>
> -- WITHIN_REP_VIEW combines the WITHIN_REP_COUNTER_VIEW and
> WITHIN_REP_RESPONSE_VIEW into one table from which across
> -- replication or other statistical summaries by replication can be produced
> CREATE VIEW JSL_DB.WITHIN_REP_VIEW (SIM_RUN_ID_FK, EXP_NAME, ELEMENT_NAME,
> STAT_NAME, REP_NUM, VALUE) AS
> (SELECT JSL_DB.WITHIN_REP_STAT.SIM_RUN_ID_FK, EXP_NAME, ELEMENT_NAME,
> STAT_NAME, REP_NUM, AVERAGE AS VALUE
> FROM (JSL_DB.SIMULATION_RUN JOIN JSL_DB.WITHIN_REP_STAT on
> JSL_DB.SIMULATION_RUN.ID = JSL_DB.WITHIN_REP_STAT.SIM_RUN_ID_FK)
> JOIN JSL_DB.MODEL_ELEMENT ON ELEMENT_ID =
> JSL_DB.WITHIN_REP_STAT.ELEMENT_ID_FK
> UNION
> SELECT JSL_DB.WITHIN_REP_COUNTER_STAT.SIM_RUN_ID_FK, EXP_NAME, ELEMENT_NAME,
> STAT_NAME, REP_NUM, LAST_VALUE as VALUE
> FROM (JSL_DB.SIMULATION_RUN JOIN JSL_DB.WITHIN_REP_COUNTER_STAT on
> JSL_DB.SIMULATION_RUN.ID = JSL_DB.WITHIN_REP_COUNTER_STAT.SIM_RUN_ID_FK)
> JOIN JSL_DB.MODEL_ELEMENT ON ELEMENT_ID =
> JSL_DB.WITHIN_REP_COUNTER_STAT.ELEMENT_ID_FK);
>
> -- PW_DIFF_WITHIN_REP_VIEW computes the pairwise differences across
> difference simulation experiments
> -- doesn't work for derby, 3-28-2019, works for postgres
> --
> -- create view JSL_DB.PW_DIFF_WITHIN_REP_VIEW
> -- as (select SIMULATION_RUN.SIM_NAME, A.SIM_RUN_ID_FK AS A_SIM_NUM,
> A.STAT_NAME, A.EXP_NAME as A_EXP_NAME, A.REP_NUM, A.VALUE as A_VALUE,
> -- B.SIM_RUN_ID_FK as B_SIM_NUM, B.EXP_NAME as B_EXP_NAME, B.VALUE as B_VALUE,
> -- '(' || A.EXP_NAME || ' - ' || B.EXP_NAME || ')' as DIFF_NAME, (A.VALUE -
> B.VALUE) as A_MINUS_B
> -- from JSL_DB.WITHIN_REP_VIEW as A, JSL_DB.WITHIN_REP_VIEW as B,
> JSL_DB.SIMULATION_RUN
> -- where A.SIM_RUN_ID_FK = JSL_DB.SIMULATION_RUN.ID
> -- and A.STAT_NAME = B.STAT_NAME
> -- and A.REP_NUM = B.REP_NUM
> -- and A.SIM_RUN_ID_FK > B.SIM_RUN_ID_FK
> -- and A.ELEMENT_NAME = B.ELEMENT_NAME);
> --
> -- create view JSL_DB.PW_DIFF_AR_REP_VIEW (SIM_NAME, STAT_NAME, A_EXP_NAME,
> B_EXP_NAME, DIFF_NAME, AVG_A, STD_DEV_A,
> -- AVG_B, STD_DEV_B, AVG_DIFF_A_MINUS_B, STD_DEV_DIFF_A_MINUS_B, STAT_COUNT)
> -- as (select SIM_NAME, STAT_NAME, A_EXP_NAME, B_EXP_NAME, DIFF_NAME,
> AVG(A_VALUE) as AVG_A, STDDEV_SAMP(A_VALUE) as STD_DEV_A,
> -- AVG(B_VALUE) as AVG_B, STDDEV_SAMP(B_VALUE) as STD_DEV_B,
> -- AVG(A_MINUS_B) as AVG_DIFF_A_MINUS_B, STDDEV_SAMP(A_MINUS_B) as
> STD_DEV_DIFF_A_MINUS_B,
> -- COUNT(A_MINUS_B) as STAT_COUNT
> -- from JSL_DB.PW_DIFF_WITHIN_REP_VIEW
> -- group by SIM_NAME, STAT_NAME, A_EXP_NAME, B_EXP_NAME, DIFF_NAME);
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (DERBY-7040) Add dependency stanzas to maven poms
[ https://issues.apache.org/jira/browse/DERBY-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas resolved DERBY-7040. -- Resolution: Fixed Fix Version/s: 10.15.1.4 > Add dependency stanzas to maven poms > > > Key: DERBY-7040 > URL: https://issues.apache.org/jira/browse/DERBY-7040 > Project: Derby > Issue Type: Improvement > Components: Build tools >Affects Versions: 10.15.1.3 >Reporter: Rick Hillegas >Priority: Major > Fix For: 10.15.1.4 > > Attachments: derby-7040-01-aa-addDependenciesToPOMs.diff > > > Add hard dependencies (from the module diagrams) to the poms under maven2. > The dependency stanza in the network server pom can be used as a template. In > particular, dependencies on derbyshared.jar should be listed. This issue was > raised by DERBY-7039. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (DERBY-7040) Add dependency stanzas to maven poms
[ https://issues.apache.org/jira/browse/DERBY-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas closed DERBY-7040. Assignee: Rick Hillegas > Add dependency stanzas to maven poms > > > Key: DERBY-7040 > URL: https://issues.apache.org/jira/browse/DERBY-7040 > Project: Derby > Issue Type: Improvement > Components: Build tools >Affects Versions: 10.15.1.3 >Reporter: Rick Hillegas >Assignee: Rick Hillegas >Priority: Major > Fix For: 10.15.1.4 > > Attachments: derby-7040-01-aa-addDependenciesToPOMs.diff > > > Add hard dependencies (from the module diagrams) to the poms under maven2. > The dependency stanza in the network server pom can be used as a template. In > particular, dependencies on derbyshared.jar should be listed. This issue was > raised by DERBY-7039. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DERBY-7040) Add dependency stanzas to maven poms
[ https://issues.apache.org/jira/browse/DERBY-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806287#comment-16806287 ] ASF subversion and git services commented on DERBY-7040: Commit 1856706 from Richard N. Hillegas in branch 'code/branches/10.15' [ https://svn.apache.org/r1856706 ] DERBY-7040: Merge 1856701 from trunk to the 10.15 branch. > Add dependency stanzas to maven poms > > > Key: DERBY-7040 > URL: https://issues.apache.org/jira/browse/DERBY-7040 > Project: Derby > Issue Type: Improvement > Components: Build tools >Affects Versions: 10.15.1.3 >Reporter: Rick Hillegas >Priority: Major > Attachments: derby-7040-01-aa-addDependenciesToPOMs.diff > > > Add hard dependencies (from the module diagrams) to the poms under maven2. > The dependency stanza in the network server pom can be used as a template. In > particular, dependencies on derbyshared.jar should be listed. This issue was > raised by DERBY-7039. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DERBY-7040) Add dependency stanzas to maven poms
[ https://issues.apache.org/jira/browse/DERBY-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806276#comment-16806276 ] ASF subversion and git services commented on DERBY-7040: Commit 1856701 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1856701 ] DERBY-7040: Add hard module dependencies to the maven poms which we publish at the end of a release; commit derby-7040-01-aa-addDependenciesToPOMs.diff. > Add dependency stanzas to maven poms > > > Key: DERBY-7040 > URL: https://issues.apache.org/jira/browse/DERBY-7040 > Project: Derby > Issue Type: Improvement > Components: Build tools >Affects Versions: 10.15.1.3 >Reporter: Rick Hillegas >Priority: Major > Attachments: derby-7040-01-aa-addDependenciesToPOMs.diff > > > Add hard dependencies (from the module diagrams) to the poms under maven2. > The dependency stanza in the network server pom can be used as a template. In > particular, dependencies on derbyshared.jar should be listed. This issue was > raised by DERBY-7039. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DERBY-7040) Add dependency stanzas to maven poms
[
https://issues.apache.org/jira/browse/DERBY-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806275#comment-16806275
]
Rick Hillegas commented on DERBY-7040:
--
Attaching derby-7040-01-aa-addDependenciesToPOMs.diff. This patch adds hard
dependencies to the maven poms which are published at the end of a release. The
hard dependencies are the non-optional dependencies from the 10.15.1 module
diagrams.
It seems that these poms are consulted by projects which use maven as their
build tool. See the commentary on DERBY-7039.
Touches the following files:
{noformat}
M maven2/client/pom.xml
M maven2/engine/pom.xml
M maven2/net/pom.xml
M maven2/optionaltools/pom.xml
M maven2/tools/pom.xml
{noformat}
> Add dependency stanzas to maven poms
>
>
> Key: DERBY-7040
> URL: https://issues.apache.org/jira/browse/DERBY-7040
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
>Affects Versions: 10.15.1.3
>Reporter: Rick Hillegas
>Priority: Major
> Attachments: derby-7040-01-aa-addDependenciesToPOMs.diff
>
>
> Add hard dependencies (from the module diagrams) to the poms under maven2.
> The dependency stanza in the network server pom can be used as a template. In
> particular, dependencies on derbyshared.jar should be listed. This issue was
> raised by DERBY-7039.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DERBY-7040) Add dependency stanzas to maven poms
[ https://issues.apache.org/jira/browse/DERBY-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-7040: - Attachment: derby-7040-01-aa-addDependenciesToPOMs.diff > Add dependency stanzas to maven poms > > > Key: DERBY-7040 > URL: https://issues.apache.org/jira/browse/DERBY-7040 > Project: Derby > Issue Type: Improvement > Components: Build tools >Affects Versions: 10.15.1.3 >Reporter: Rick Hillegas >Priority: Major > Attachments: derby-7040-01-aa-addDependenciesToPOMs.diff > > > Add hard dependencies (from the module diagrams) to the poms under maven2. > The dependency stanza in the network server pom can be used as a template. In > particular, dependencies on derbyshared.jar should be listed. This issue was > raised by DERBY-7039. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Derby wiki will be migrating to new URLs this spring
Hey Bryan, I couldn't figure out how to help out, based on the conversation on https://issues.apache.org/jira/browse/INFRA-18081. It seems that you and Gavin need to sort out some preliminary bits first. Let me know when and how I can help. Thanks, -Rick On 3/23/19 9:15 AM, Bryan Pendleton wrote: Reminder: I'm working on converting the db-derby moin wiki to the new Derby confluence space. Please don't make any changes to either space right now; I will send out a message when I've successfully migrated the wiki. For now, I'm having a little trouble with the tools: INFRA-18081 if you want to follow along. thanks, bryan On Tue, Mar 5, 2019 at 7:35 PM Bryan Pendleton wrote: Hi all, Quoting from an internal Apache email: "As you may be aware moin wiki service has been deprecated for some time now - we have not been accepting new moin wikis. " "Infra has decided to close down the service, and so all projects that still have a moin wiki are being asked to migrate away to Confluence. We have set a deadline of May 31st, 3 months from now" The Derby wiki (https://wiki.apache.org/db-derby/) is a MoinMoin wiki. The purpose of this mail is: 1) To let people know that we're going to need to migrate the Derby wiki. 2) To find out if anyone can help with this task: there is a migration tool that will hopefully do most of the mechanical steps for us, but then we need some folks to sign on to the new wiki, make sure that the conversion has gone successfully, fix problems that are present after the conversion, help us find broken links that need to be changed, etc. 3) To propose that I will make a first attempt at using the wiki conversion tool over the weekend of Mar 22nd, 2019. Please let us know any feedback or ideas. thanks, bryan
[jira] [Commented] (DERBY-7041) null pointer exception when creating view based on other views
[
https://issues.apache.org/jira/browse/DERBY-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16806178#comment-16806178
]
Rick Hillegas commented on DERBY-7041:
--
The stack trace shows that the CREATE VIEW statement incurs an NPE while trying
to record a persistent dependency of the view on the STDDEV_SAMP aggregate:
{noformat}
java.lang.NullPointerException
at java.base/java.util.Hashtable.put(Hashtable.java:479)
at
org.apache.derby.iapi.sql.depend.ProviderList.addProvider(ProviderList.java:42)
at
org.apache.derby.impl.sql.compile.CompilerContextImpl.addProviderToAuxiliaryList(CompilerContextImpl.java:319)
at
org.apache.derby.impl.sql.compile.CompilerContextImpl.createDependency(CompilerContextImpl.java:290)
at
org.apache.derby.impl.sql.compile.AggregateNode.bindExpression(AggregateNode.java:404)
at
org.apache.derby.impl.sql.compile.JavaToSQLValueNode.bindExpression(JavaToSQLValueNode.java:237)
at
org.apache.derby.impl.sql.compile.ResultColumn.bindExpression(ResultColumn.java:759)
at
org.apache.derby.impl.sql.compile.ResultColumnList.bindExpressions(ResultColumnList.java:839)
at
org.apache.derby.impl.sql.compile.SelectNode.bindExpressions(SelectNode.java:575)
at
org.apache.derby.impl.sql.compile.CreateViewNode.bindViewDefinition(CreateViewNode.java:255)
at
org.apache.derby.impl.sql.compile.CreateViewNode.bindStatement(CreateViewNode.java:175)
at
org.apache.derby.impl.sql.GenericStatement.prepMinion(GenericStatement.java:401)
at
org.apache.derby.impl.sql.GenericStatement.prepare(GenericStatement.java:99)
at
org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepareInternalStatement(GenericLanguageConnectionContext.java:1114)
at
org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:689)
at
org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:637)
at org.apache.derby.impl.tools.ij.ij.executeImmediate(ij.java:372)
at org.apache.derby.impl.tools.ij.utilMain.doCatch(utilMain.java:534)
at
org.apache.derby.impl.tools.ij.utilMain.runScriptGuts(utilMain.java:375)
at org.apache.derby.impl.tools.ij.utilMain.go(utilMain.java:251)
at org.apache.derby.impl.tools.ij.Main.go(Main.java:229)
at org.apache.derby.impl.tools.ij.Main.mainCore(Main.java:184)
at org.apache.derby.impl.tools.ij.Main.main(Main.java:75)
at org.apache.derby.tools.ij.main(ij.java:59)
{noformat}
This happens because we implemented the statistical aggregates as user defined
aggregates and because the aggregate descriptor has a NULL object ID.
Two things look odd here and could serve as the basis for a fix:
* There should be no need to declare a persistent dependency between a
user-defined view and a system-supplied aggregate.
* The aggregate descriptor, nonetheless, should have a real object ID.
> null pointer exception when creating view based on other views
> --
>
> Key: DERBY-7041
> URL: https://issues.apache.org/jira/browse/DERBY-7041
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.14.2.0
> Environment: max os x , intellij
>Reporter: Manuel Rossetti
>Priority: Major
> Attachments: JSLDb.sql, JSLDb.sql, JSLDb_DriveThroughPharmacy.zip,
> derby-7041.sql
>
>
> I can execute a SELECT query that works but when I try to create a view on
> that select query, I simply get a java null pointer exception with no
> details. I have tested the same statements on a postgres database and they
> worked without error.
> Below, the PW_DIFF_WITHIN_REP_VIEW create does work, but the
> PW_DIFF_AR_REP_VIEW does not. Again, the SELECT clause of
> PW_DIFF_AR_REP_VIEW will work, but when used within the create clause the
> error occurs.
> I have attached the entire database creation script and an embedded instance
> that can be used for testing. It has data.
>
> -- WITHIN_REP_VIEW combines the WITHIN_REP_COUNTER_VIEW and
> WITHIN_REP_RESPONSE_VIEW into one table from which across
> -- replication or other statistical summaries by replication can be produced
> CREATE VIEW JSL_DB.WITHIN_REP_VIEW (SIM_RUN_ID_FK, EXP_NAME, ELEMENT_NAME,
> STAT_NAME, REP_NUM, VALUE) AS
> (SELECT JSL_DB.WITHIN_REP_STAT.SIM_RUN_ID_FK, EXP_NAME, ELEMENT_NAME,
> STAT_NAME, REP_NUM, AVERAGE AS VALUE
> FROM (JSL_DB.SIMULATION_RUN JOIN JSL_DB.WITHIN_REP_STAT on
> JSL_DB.SIMULATION_RUN.ID = JSL_DB.WITHIN_REP_STAT.SIM_RUN_ID_FK)
> JOIN JSL_DB.MODEL_ELEMENT ON ELEMENT_ID =
> JSL_DB.WITHIN_REP_STAT.ELEMENT_ID_FK
> UNION
> SELECT JSL_DB.WITHIN_REP_COUNTER_STAT.SIM_RUN_ID_FK, EXP_NAME, ELEMENT_NAME,
> STAT_NAME, REP_NUM, LAST_VALUE as VALUE
> FROM (JSL_D
