[jira] [Commented] (DERBY-6910) Add Option for column names in first line of export file when using CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE
[ https://issues.apache.org/jira/browse/DERBY-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185885#comment-16185885 ] Lashan Faliq commented on DERBY-6910: - Hello RIck, Should i try to work on this from a different approach or should i drop this issue? Thank you > Add Option for column names in first line of export file when using CALL > SYSCS_UTIL.SYSCS_EXPORT_TABLE > -- > > Key: DERBY-6910 > URL: https://issues.apache.org/jira/browse/DERBY-6910 > Project: Derby > Issue Type: Improvement > Components: Tools >Affects Versions: 10.12.1.1 >Reporter: Christian Eugster >Assignee: Lashan Faliq >Priority: Trivial > Attachments: DERBY-6910Enhancement.diff > > > It would be fine if there was the Option for adding the columnnames in the > first line of an Export file in CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6910) Add Option for column names in first line of export file when using CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE
[ https://issues.apache.org/jira/browse/DERBY-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184928#comment-16184928 ] Lashan Faliq commented on DERBY-6910: - Rather than adding the functionality to SYSCS_UTIL.SYSCS_EXPORT_TABLE i have created a new method SYSCS_UTIL.SYSCS_EXPORT_COLUMN which exports a column in a table to a file. > Add Option for column names in first line of export file when using CALL > SYSCS_UTIL.SYSCS_EXPORT_TABLE > -- > > Key: DERBY-6910 > URL: https://issues.apache.org/jira/browse/DERBY-6910 > Project: Derby > Issue Type: Improvement > Components: Tools >Affects Versions: 10.12.1.1 >Reporter: Christian Eugster >Assignee: Lashan Faliq >Priority: Trivial > > It would be fine if there was the Option for adding the columnnames in the > first line of an Export file in CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (DERBY-6910) Add Option for column names in first line of export file when using CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE
[ https://issues.apache.org/jira/browse/DERBY-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lashan Faliq updated DERBY-6910: Attachment: DERBY-6910Enhancement.diff The patch for the above mentioned enhancement let me know if it is ok. > Add Option for column names in first line of export file when using CALL > SYSCS_UTIL.SYSCS_EXPORT_TABLE > -- > > Key: DERBY-6910 > URL: https://issues.apache.org/jira/browse/DERBY-6910 > Project: Derby > Issue Type: Improvement > Components: Tools >Affects Versions: 10.12.1.1 >Reporter: Christian Eugster >Assignee: Lashan Faliq >Priority: Trivial > Attachments: DERBY-6910Enhancement.diff > > > It would be fine if there was the Option for adding the columnnames in the > first line of an Export file in CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (DERBY-6957) ERROR 40XL1: A lock could not be obtained within the time requested for alter or truncate table
[ https://issues.apache.org/jira/browse/DERBY-6957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lashan Faliq reassigned DERBY-6957: --- Assignee: (was: Lashan Faliq) > ERROR 40XL1: A lock could not be obtained within the time requested for alter > or truncate table > --- > > Key: DERBY-6957 > URL: https://issues.apache.org/jira/browse/DERBY-6957 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.13.1.1 > Environment: production >Reporter: SUNEEL KUMAR OLETI > > hi, > for all my Drop table, alter table, truncate table i am getting below error. > ERROR 40XL1: A lock could not be obtained within the time requested > at org.apache.derby.iapi.error.StandardException.newException(Unknown > Source) > at org.apache.derby.iapi.error.StandardException.newException(Unknown > Source) > at > org.apache.derby.impl.services.locks.ConcurrentLockSet.lockObject(Unknown > Source) > at org.apache.derby.impl.services.locks.AbstractPool.lockObject(Unknown > Source) > at > org.apache.derby.impl.services.locks.ConcurrentPool.lockObject(Unknown Source) > at > org.apache.derby.impl.store.raw.xact.ContainerLocking3.lockContainer(Unknown > Source) > at > org.apache.derby.impl.store.raw.data.BaseContainerHandle.useContainer(Unknown > Source) > at > org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown > Source) > at > org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown > Source) > at org.apache.derby.impl.store.raw.xact.Xact.openContainer(Unknown > Source) > at > org.apache.derby.impl.store.access.conglomerate.OpenConglomerate.init(Unknown > Source) > at org.apache.derby.impl.store.access.heap.Heap.open(Unknown Source) > at > org.apache.derby.impl.store.access.RAMTransaction.openConglomerate(Unknown > Source) > at > org.apache.derby.impl.store.access.RAMTransaction.openConglomerate(Unknown > Source) > at > org.apache.derby.impl.sql.execute.DDLConstantAction.lockTableForDDL(Unknown > Source) > at > org.apache.derby.impl.sql.execute.AlterTableConstantAction.executeConstantActionBody(Unknown > Source) > at > org.apache.derby.impl.sql.execute.AlterTableConstantAction.executeConstantAction(Unknown > Source) > at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown Source) > at > org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source) > at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown > Source) > at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown > Source) > at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeLargeUpdate(Unknown > Source) > at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown > Source) > at com.db.UpdateTables.alterDataTable(UpdateTables.java:1833) > at > com.he.webApiLayer.ResponseBuilder.insertDataInDB(ResponseBuilder.java:2910) > at com.he.webApiLayer.InputAPI.lambda$1(InputAPI.java:127) > at spark.RouteImpl$1.handle(RouteImpl.java:61) > at spark.http.matching.Routes.execute(Routes.java:61) > at spark.http.matching.MatcherFilter.doFilter(MatcherFilter.java:128) > at > spark.embeddedserver.jetty.JettyHandler.doHandle(JettyHandler.java:50) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:119) > at org.eclipse.jetty.server.Server.handle(Server.java:517) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:242) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:261) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:75) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:213) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:147) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654) > at >
[jira] [Assigned] (DERBY-6957) ERROR 40XL1: A lock could not be obtained within the time requested for alter or truncate table
[ https://issues.apache.org/jira/browse/DERBY-6957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lashan Faliq reassigned DERBY-6957: --- Assignee: Lashan Faliq > ERROR 40XL1: A lock could not be obtained within the time requested for alter > or truncate table > --- > > Key: DERBY-6957 > URL: https://issues.apache.org/jira/browse/DERBY-6957 > Project: Derby > Issue Type: Bug > Components: JDBC >Affects Versions: 10.13.1.1 > Environment: production >Reporter: SUNEEL KUMAR OLETI >Assignee: Lashan Faliq > > hi, > for all my Drop table, alter table, truncate table i am getting below error. > ERROR 40XL1: A lock could not be obtained within the time requested > at org.apache.derby.iapi.error.StandardException.newException(Unknown > Source) > at org.apache.derby.iapi.error.StandardException.newException(Unknown > Source) > at > org.apache.derby.impl.services.locks.ConcurrentLockSet.lockObject(Unknown > Source) > at org.apache.derby.impl.services.locks.AbstractPool.lockObject(Unknown > Source) > at > org.apache.derby.impl.services.locks.ConcurrentPool.lockObject(Unknown Source) > at > org.apache.derby.impl.store.raw.xact.ContainerLocking3.lockContainer(Unknown > Source) > at > org.apache.derby.impl.store.raw.data.BaseContainerHandle.useContainer(Unknown > Source) > at > org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown > Source) > at > org.apache.derby.impl.store.raw.data.BaseDataFileFactory.openContainer(Unknown > Source) > at org.apache.derby.impl.store.raw.xact.Xact.openContainer(Unknown > Source) > at > org.apache.derby.impl.store.access.conglomerate.OpenConglomerate.init(Unknown > Source) > at org.apache.derby.impl.store.access.heap.Heap.open(Unknown Source) > at > org.apache.derby.impl.store.access.RAMTransaction.openConglomerate(Unknown > Source) > at > org.apache.derby.impl.store.access.RAMTransaction.openConglomerate(Unknown > Source) > at > org.apache.derby.impl.sql.execute.DDLConstantAction.lockTableForDDL(Unknown > Source) > at > org.apache.derby.impl.sql.execute.AlterTableConstantAction.executeConstantActionBody(Unknown > Source) > at > org.apache.derby.impl.sql.execute.AlterTableConstantAction.executeConstantAction(Unknown > Source) > at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown Source) > at > org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source) > at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown > Source) > at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown > Source) > at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown > Source) > at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeLargeUpdate(Unknown > Source) > at > org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeUpdate(Unknown > Source) > at com.db.UpdateTables.alterDataTable(UpdateTables.java:1833) > at > com.he.webApiLayer.ResponseBuilder.insertDataInDB(ResponseBuilder.java:2910) > at com.he.webApiLayer.InputAPI.lambda$1(InputAPI.java:127) > at spark.RouteImpl$1.handle(RouteImpl.java:61) > at spark.http.matching.Routes.execute(Routes.java:61) > at spark.http.matching.MatcherFilter.doFilter(MatcherFilter.java:128) > at > spark.embeddedserver.jetty.JettyHandler.doHandle(JettyHandler.java:50) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:119) > at org.eclipse.jetty.server.Server.handle(Server.java:517) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:242) > at > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:261) > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95) > at > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:75) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:213) > at > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:147) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654) > at >
[jira] [Assigned] (DERBY-6951) ClientPreparedStatement may be buggy
[
https://issues.apache.org/jira/browse/DERBY-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lashan Faliq reassigned DERBY-6951:
---
Assignee: Lashan Faliq
> ClientPreparedStatement may be buggy
>
>
> Key: DERBY-6951
> URL: https://issues.apache.org/jira/browse/DERBY-6951
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Reporter: Hao Zhong
>Assignee: Lashan Faliq
>
> DERBY-1610 fixed some bugs in PreparedStatement.java. I find that the buggy
> file is similar to ClientPreparedStatement.java. For example, both files have
> the following code:
> {code}
> public void setBigDecimal(int parameterIndex, java.math.BigDecimal x) throws
> SQLException {
> try
> {
> synchronized (connection_) {
> if (agent_.loggingEnabled()) {
> agent_.logWriter_.traceEntry(this, "setBigDecimal",
> parameterIndex, x);
> }
>
> final int paramType =
> getColumnMetaDataX().getColumnType(parameterIndex);
> ...
> }
> catch ( SqlException se )
> {
> throw se.getSQLException();
> }
> }
> {code}
> The fixed code is as follow:
> {code}
> public void setBigDecimal(int parameterIndex, java.math.BigDecimal x) throws
> SQLException {
> try
> {
> synchronized (connection_) {
> if (agent_.loggingEnabled()) {
> agent_.logWriter_.traceEntry(this, "setBigDecimal",
> parameterIndex, x);
> }
>
> final int paramType =
> getColumnMetaDataX().getColumnType(
> checkForEscapedCallWithResult( parameterIndex ) );
> ...
> }
> catch ( SqlException se )
> {
> throw se.getSQLException();
> }
> }
> {code}
> The repair can be applied to ClientPreparedStatement.java
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (DERBY-6910) Add Option for column names in first line of export file when using CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE
[ https://issues.apache.org/jira/browse/DERBY-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lashan Faliq reassigned DERBY-6910: --- Assignee: Lashan Faliq > Add Option for column names in first line of export file when using CALL > SYSCS_UTIL.SYSCS_EXPORT_TABLE > -- > > Key: DERBY-6910 > URL: https://issues.apache.org/jira/browse/DERBY-6910 > Project: Derby > Issue Type: Improvement > Components: Tools >Affects Versions: 10.12.1.1 >Reporter: Christian Eugster >Assignee: Lashan Faliq >Priority: Trivial > > It would be fine if there was the Option for adding the columnnames in the > first line of an Export file in CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DERBY-6395) SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER TABLE' cannot be performed
[
https://issues.apache.org/jira/browse/DERBY-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169581#comment-16169581
]
Lashan Faliq commented on DERBY-6395:
-
i attached the new patch with the test case can you please check it and let me
know Thank you.
> SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER
> TABLE' cannot be performed
>
>
> Key: DERBY-6395
> URL: https://issues.apache.org/jira/browse/DERBY-6395
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.11.1.1
>Reporter: Kathey Marsden
>Assignee: Lashan Faliq
>Priority: Trivial
> Attachments: derby6395fix.diff, derby6395WithTestCases.diff
>
>
> For historical reasons SYCSCS_UTIL.SYSCS_COMPRESS_TABLE gives a not very
> sensible message. The user did not actually execute an ALTER TABLE command.
> ij> CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP','NOTTHERE',1);
> ERROR 38000: The exception 'java.sql.SQLException: 'ALTER TABLE' cannot be
> performed on 'APP.NOTTHERE' because it does n
> ot exist.' was thrown while evaluating an expression.
> ERROR 42Y55: 'ALTER TABLE' cannot be performed on 'APP.NOTTHERE' because it
> does not exist.
> ij>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (DERBY-6395) SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER TABLE' cannot be performed
[
https://issues.apache.org/jira/browse/DERBY-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lashan Faliq updated DERBY-6395:
Attachment: derby6395WithTestCases.diff
> SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER
> TABLE' cannot be performed
>
>
> Key: DERBY-6395
> URL: https://issues.apache.org/jira/browse/DERBY-6395
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.11.1.1
>Reporter: Kathey Marsden
>Assignee: Lashan Faliq
>Priority: Trivial
> Attachments: derby6395fix.diff, derby6395WithTestCases.diff
>
>
> For historical reasons SYCSCS_UTIL.SYSCS_COMPRESS_TABLE gives a not very
> sensible message. The user did not actually execute an ALTER TABLE command.
> ij> CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP','NOTTHERE',1);
> ERROR 38000: The exception 'java.sql.SQLException: 'ALTER TABLE' cannot be
> performed on 'APP.NOTTHERE' because it does n
> ot exist.' was thrown while evaluating an expression.
> ERROR 42Y55: 'ALTER TABLE' cannot be performed on 'APP.NOTTHERE' because it
> does not exist.
> ij>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DERBY-6395) SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER TABLE' cannot be performed
[
https://issues.apache.org/jira/browse/DERBY-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169308#comment-16169308
]
Lashan Faliq commented on DERBY-6395:
-
i added a test to compressTable.sql
{code:java}
--test case for derby 6395
--perfoming compress table when there is no table
--gives incorrect error
--This should generate an error 'Compress table cannot be performed on TABLE
because it does not exist.'
CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP','testTable',1);
--Now we create a table
create table testTable (ID INT PRIMARY KEY,
NAME VARCHAR(12));
--This should not generate any error since we created a table called 'table'
CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP','testTable',1);
drop table testTable;
--end of derby 6395
{code}
And then i tried running the test as shown in the link , at first i got the
error that there was no build file but then i added the build file i had in my
duplicate trunk in the same location and now it says that
BUILD FAILED
Target "org.apache.derbyTesting.functionTests.tests.lang.TriggerWhenClauseTest"
does not exist in the project "null".
Can you please guide me on what i should do next? do i need to create a new
build.xml ?
> SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER
> TABLE' cannot be performed
>
>
> Key: DERBY-6395
> URL: https://issues.apache.org/jira/browse/DERBY-6395
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.11.1.1
>Reporter: Kathey Marsden
>Assignee: Lashan Faliq
>Priority: Trivial
> Attachments: derby6395fix.diff
>
>
> For historical reasons SYCSCS_UTIL.SYSCS_COMPRESS_TABLE gives a not very
> sensible message. The user did not actually execute an ALTER TABLE command.
> ij> CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP','NOTTHERE',1);
> ERROR 38000: The exception 'java.sql.SQLException: 'ALTER TABLE' cannot be
> performed on 'APP.NOTTHERE' because it does n
> ot exist.' was thrown while evaluating an expression.
> ERROR 42Y55: 'ALTER TABLE' cannot be performed on 'APP.NOTTHERE' because it
> does not exist.
> ij>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (DERBY-6395) SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER TABLE' cannot be performed
[
https://issues.apache.org/jira/browse/DERBY-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155320#comment-16155320
]
Lashan Faliq edited comment on DERBY-6395 at 9/6/17 1:25 PM:
-
I ran java org.apache.derbyTesting.functionTests.harness.RunSuite derbyall and
the report showed that there were no failures.
Here to fix the bug i first checked if the table existed using the below code.
{code:java}
Connection connection = getDefaultConn();
+ boolean tableExists=false;
+ DatabaseMetaData md = connection.getMetaData();
+ ResultSet rs = md.getTables(null, null, "%", null);
+ while (rs.next()) {
+ if(tablename.equals(rs.getString(3))){
+ tableExists=true;
+ }
+ }
{code}
If it existed i just called existing code if not
{code:java}
else{
+ System.out.println("Compress table cannot be performed
on "+tablename+" because it does not exist.");
+ }
}
{code}
And i have attached the patch for the fix.
was (Author: lashan faliq):
I ran java org.apache.derbyTesting.functionTests.harness.RunSuite derbyall and
the report showed that there were no failures.
Here to fix the bug i first checked if the table existed using the below code.
{code:java}
Connection connection = getDefaultConn();
+ boolean tableExists=false;
+ DatabaseMetaData md = connection.getMetaData();
+ ResultSet rs = md.getTables(null, null, "%", null);
+ while (rs.next()) {
+ if(tablename.equals(rs.getString(3))){
+ tableExists=true;
+ }
+ }
{code}
If it existed i just called existing code if not
{code:java}
else{
+ System.out.println("Compress table cannot be performed
on "+tablename+" because it does not exist.");
+ }
}
{code}
> SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER
> TABLE' cannot be performed
>
>
> Key: DERBY-6395
> URL: https://issues.apache.org/jira/browse/DERBY-6395
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.11.1.1
>Reporter: Kathey Marsden
>Assignee: Lashan Faliq
>Priority: Trivial
> Attachments: derby6395fix.diff
>
>
> For historical reasons SYCSCS_UTIL.SYSCS_COMPRESS_TABLE gives a not very
> sensible message. The user did not actually execute an ALTER TABLE command.
> ij> CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP','NOTTHERE',1);
> ERROR 38000: The exception 'java.sql.SQLException: 'ALTER TABLE' cannot be
> performed on 'APP.NOTTHERE' because it does n
> ot exist.' was thrown while evaluating an expression.
> ERROR 42Y55: 'ALTER TABLE' cannot be performed on 'APP.NOTTHERE' because it
> does not exist.
> ij>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (DERBY-6395) SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER TABLE' cannot be performed
[
https://issues.apache.org/jira/browse/DERBY-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lashan Faliq updated DERBY-6395:
Attachment: derby6395fix.diff
I ran java org.apache.derbyTesting.functionTests.harness.RunSuite derbyall and
the report showed that there were no failures.
Here to fix the bug i first checked if the table existed using the below code.
{code:java}
Connection connection = getDefaultConn();
+ boolean tableExists=false;
+ DatabaseMetaData md = connection.getMetaData();
+ ResultSet rs = md.getTables(null, null, "%", null);
+ while (rs.next()) {
+ if(tablename.equals(rs.getString(3))){
+ tableExists=true;
+ }
+ }
{code}
If it existed i just called existing code if not
{code:java}
else{
+ System.out.println("Compress table cannot be performed
on "+tablename+" because it does not exist.");
+ }
}
{code}
> SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER
> TABLE' cannot be performed
>
>
> Key: DERBY-6395
> URL: https://issues.apache.org/jira/browse/DERBY-6395
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.11.1.1
>Reporter: Kathey Marsden
>Assignee: Lashan Faliq
>Priority: Trivial
> Attachments: derby6395fix.diff
>
>
> For historical reasons SYCSCS_UTIL.SYSCS_COMPRESS_TABLE gives a not very
> sensible message. The user did not actually execute an ALTER TABLE command.
> ij> CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP','NOTTHERE',1);
> ERROR 38000: The exception 'java.sql.SQLException: 'ALTER TABLE' cannot be
> performed on 'APP.NOTTHERE' because it does n
> ot exist.' was thrown while evaluating an expression.
> ERROR 42Y55: 'ALTER TABLE' cannot be performed on 'APP.NOTTHERE' because it
> does not exist.
> ij>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (DERBY-6395) SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER TABLE' cannot be performed
[
https://issues.apache.org/jira/browse/DERBY-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lashan Faliq updated DERBY-6395:
Attachment: (was: derby6395fix.diff)
> SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER
> TABLE' cannot be performed
>
>
> Key: DERBY-6395
> URL: https://issues.apache.org/jira/browse/DERBY-6395
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.11.1.1
>Reporter: Kathey Marsden
>Assignee: Lashan Faliq
>Priority: Trivial
>
> For historical reasons SYCSCS_UTIL.SYSCS_COMPRESS_TABLE gives a not very
> sensible message. The user did not actually execute an ALTER TABLE command.
> ij> CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP','NOTTHERE',1);
> ERROR 38000: The exception 'java.sql.SQLException: 'ALTER TABLE' cannot be
> performed on 'APP.NOTTHERE' because it does n
> ot exist.' was thrown while evaluating an expression.
> ERROR 42Y55: 'ALTER TABLE' cannot be performed on 'APP.NOTTHERE' because it
> does not exist.
> ij>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (DERBY-6395) SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER TABLE' cannot be performed
[
https://issues.apache.org/jira/browse/DERBY-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lashan Faliq updated DERBY-6395:
Attachment: (was: corrected error.png)
> SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER
> TABLE' cannot be performed
>
>
> Key: DERBY-6395
> URL: https://issues.apache.org/jira/browse/DERBY-6395
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.11.1.1
>Reporter: Kathey Marsden
>Assignee: Lashan Faliq
>Priority: Trivial
>
> For historical reasons SYCSCS_UTIL.SYSCS_COMPRESS_TABLE gives a not very
> sensible message. The user did not actually execute an ALTER TABLE command.
> ij> CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP','NOTTHERE',1);
> ERROR 38000: The exception 'java.sql.SQLException: 'ALTER TABLE' cannot be
> performed on 'APP.NOTTHERE' because it does n
> ot exist.' was thrown while evaluating an expression.
> ERROR 42Y55: 'ALTER TABLE' cannot be performed on 'APP.NOTTHERE' because it
> does not exist.
> ij>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (DERBY-6395) SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER TABLE' cannot be performed
[
https://issues.apache.org/jira/browse/DERBY-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lashan Faliq updated DERBY-6395:
Attachment: (was: patch.png)
> SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER
> TABLE' cannot be performed
>
>
> Key: DERBY-6395
> URL: https://issues.apache.org/jira/browse/DERBY-6395
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.11.1.1
>Reporter: Kathey Marsden
>Assignee: Lashan Faliq
>Priority: Trivial
>
> For historical reasons SYCSCS_UTIL.SYSCS_COMPRESS_TABLE gives a not very
> sensible message. The user did not actually execute an ALTER TABLE command.
> ij> CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP','NOTTHERE',1);
> ERROR 38000: The exception 'java.sql.SQLException: 'ALTER TABLE' cannot be
> performed on 'APP.NOTTHERE' because it does n
> ot exist.' was thrown while evaluating an expression.
> ERROR 42Y55: 'ALTER TABLE' cannot be performed on 'APP.NOTTHERE' because it
> does not exist.
> ij>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (DERBY-6395) SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER TABLE' cannot be performed
[
https://issues.apache.org/jira/browse/DERBY-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lashan Faliq updated DERBY-6395:
Attachment: derby6395fix.diff
> SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER
> TABLE' cannot be performed
>
>
> Key: DERBY-6395
> URL: https://issues.apache.org/jira/browse/DERBY-6395
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.11.1.1
>Reporter: Kathey Marsden
>Assignee: Lashan Faliq
>Priority: Trivial
> Attachments: corrected error.png, derby6395fix.diff, patch.png
>
>
> For historical reasons SYCSCS_UTIL.SYSCS_COMPRESS_TABLE gives a not very
> sensible message. The user did not actually execute an ALTER TABLE command.
> ij> CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP','NOTTHERE',1);
> ERROR 38000: The exception 'java.sql.SQLException: 'ALTER TABLE' cannot be
> performed on 'APP.NOTTHERE' because it does n
> ot exist.' was thrown while evaluating an expression.
> ERROR 42Y55: 'ALTER TABLE' cannot be performed on 'APP.NOTTHERE' because it
> does not exist.
> ij>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (DERBY-6395) SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER TABLE' cannot be performed
[
https://issues.apache.org/jira/browse/DERBY-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133982#comment-16133982
]
Lashan Faliq commented on DERBY-6395:
-
The patch is attached below with all the tests.
!patch.png!
The corrected issue
!corrected error.png!
i have uploaded the test to a drive since they wont let me attach a rar file.
https://drive.google.com/drive/folders/0B54oc6UMXehdbzZTb2p2VzNPeXM?usp=sharing
I have trouble understanding the tests so can you please help me see if the
test cases pass and if my implementation is ok.
Thank you
> SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER
> TABLE' cannot be performed
>
>
> Key: DERBY-6395
> URL: https://issues.apache.org/jira/browse/DERBY-6395
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.11.1.1
>Reporter: Kathey Marsden
>Assignee: Lashan Faliq
>Priority: Trivial
> Attachments: corrected error.png, patch.png
>
>
> For historical reasons SYCSCS_UTIL.SYSCS_COMPRESS_TABLE gives a not very
> sensible message. The user did not actually execute an ALTER TABLE command.
> ij> CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP','NOTTHERE',1);
> ERROR 38000: The exception 'java.sql.SQLException: 'ALTER TABLE' cannot be
> performed on 'APP.NOTTHERE' because it does n
> ot exist.' was thrown while evaluating an expression.
> ERROR 42Y55: 'ALTER TABLE' cannot be performed on 'APP.NOTTHERE' because it
> does not exist.
> ij>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (DERBY-6395) SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER TABLE' cannot be performed
[
https://issues.apache.org/jira/browse/DERBY-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lashan Faliq updated DERBY-6395:
Attachment: patch.png
> SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER
> TABLE' cannot be performed
>
>
> Key: DERBY-6395
> URL: https://issues.apache.org/jira/browse/DERBY-6395
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.11.1.1
>Reporter: Kathey Marsden
>Assignee: Lashan Faliq
>Priority: Trivial
> Attachments: corrected error.png, patch.png
>
>
> For historical reasons SYCSCS_UTIL.SYSCS_COMPRESS_TABLE gives a not very
> sensible message. The user did not actually execute an ALTER TABLE command.
> ij> CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP','NOTTHERE',1);
> ERROR 38000: The exception 'java.sql.SQLException: 'ALTER TABLE' cannot be
> performed on 'APP.NOTTHERE' because it does n
> ot exist.' was thrown while evaluating an expression.
> ERROR 42Y55: 'ALTER TABLE' cannot be performed on 'APP.NOTTHERE' because it
> does not exist.
> ij>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (DERBY-6395) SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER TABLE' cannot be performed
[
https://issues.apache.org/jira/browse/DERBY-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lashan Faliq updated DERBY-6395:
Attachment: corrected error.png
> SYSCS_UTIL.SYSCS_COMPRESS_TABLE message for not found table says: 'ALTER
> TABLE' cannot be performed
>
>
> Key: DERBY-6395
> URL: https://issues.apache.org/jira/browse/DERBY-6395
> Project: Derby
> Issue Type: Bug
> Components: SQL
>Affects Versions: 10.11.1.1
>Reporter: Kathey Marsden
>Assignee: Lashan Faliq
>Priority: Trivial
> Attachments: corrected error.png, patch.png
>
>
> For historical reasons SYCSCS_UTIL.SYSCS_COMPRESS_TABLE gives a not very
> sensible message. The user did not actually execute an ALTER TABLE command.
> ij> CALL SYSCS_UTIL.SYSCS_COMPRESS_TABLE('APP','NOTTHERE',1);
> ERROR 38000: The exception 'java.sql.SQLException: 'ALTER TABLE' cannot be
> performed on 'APP.NOTTHERE' because it does n
> ot exist.' was thrown while evaluating an expression.
> ERROR 42Y55: 'ALTER TABLE' cannot be performed on 'APP.NOTTHERE' because it
> does not exist.
> ij>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
