You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Ashitkin Alexander (JIRA)" <ji...@apache.org> on 2008/12/30 09:38:44 UTC
[jira] Created: (DERBY-3999) Can't execute select statement with
blob in network server mode
Can't execute select statement with blob in network server mode
----------------------------------------------------------------
Key: DERBY-3999
URL: https://issues.apache.org/jira/browse/DERBY-3999
Project: Derby
Issue Type: Bug
Components: Network Client
Affects Versions: 10.4.2.0
Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
Reporter: Ashitkin Alexander
Priority: Minor
When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
SELECT
this_.ID as ID11_2_,
this_.PROTOCOL_ID as PROTOCOL2_11_2_,
this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
this_.STORAGE as STORAGE11_2_,
schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
schemavali2_.ID as ID4_,
schemavali2_.ID as ID12_0_,
schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
schemavali2_.FILE_NAME as FILE3_12_0_,
schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
validation3_.ID as ID5_,
validation3_.ID as ID13_1_,
validation3_.IS_IMPORTED as IS2_13_1_,
validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
validation3_.ITEM_TEXT as ITEM4_13_1_,
validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
validation3_.RULE_NAME as RULE6_13_1_,
validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
validation3_.ISSUE_STATUS as ISSUE7_13_1_
FROM
VL_PROTOCOL_VALIDATION this_
LEFT OUTER JOIN
VL_SCHEMA_VALIDATION schemavali2_
ON
this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
LEFT OUTER JOIN
VL_SCHEMA_VALIDATION_ISSUE validation3_
ON
schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
WHERE
this_.PROTOCOL_NAME='base'
Tables ddl:
create table VL_PROTOCOL_VALIDATION (
ID integer generated always as identity(start with 1, increment by 1) primary key,
PROTOCOL_ID integer,
PROTOCOL_NAME varchar(100),
PROTOCOL_VERSION varchar(100),
STORAGE varchar(20)
);
create table VL_SCHEMA_VALIDATION (
ID integer generated always as identity(start with 1, increment by 1) primary key,
PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
FILE_NAME varchar(250),
BINARY_CONTENT blob
);
create table VL_SCHEMA_VALIDATION_ISSUE (
ID integer generated always as identity(start with 1, increment by 1) primary key,
SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
ITEM_TEXT varchar(1000),
RULE_NAME varchar(100),
ISSUE_STATUS varchar(10),
PROPERTY_NAME varchar(100),
IS_IMPORTED varchar(10),
IMPORTED_FILE_NAME varchar(250)
);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (DERBY-3999) Can't execute select
statement with blob in network server mode
Posted by "Ashitkin Alexander (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660089#action_12660089 ]
ashitkin.alexander edited comment on DERBY-3999 at 12/31/08 12:30 PM:
----------------------------------------------------------------------
ok. i will try to trace error, but you shouldn't rely on this.
was (Author: ashitkin.alexander):
yes, i can, but only after holidays - after 3-rd January. Also, as far as i remember, there was no any exception message and nо any useful information in trace. So, i'm not sure i'll find someting useful, but i'll try.
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3999) Can't execute select statement with
blob in network server mode
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724732#action_12724732 ]
Dag H. Wanvik commented on DERBY-3999:
--------------------------------------
+1 to close, since we have no repro.
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
> Attachments: d3999.sql, log.txt
>
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3999) Can't execute select statement with
blob in network server mode
Posted by "Ashitkin Alexander (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660445#action_12660445 ]
Ashitkin Alexander commented on DERBY-3999:
-------------------------------------------
I attached a log. The log isn't very useful because it looks like the derby client logs nothing internally (i use log4j ).
regarding your previous comment - i still can reproduce error, but i investigated an interesting issue:
query with additional restriction 'and length(schemavali2_.BINARY_CONTENT)<41181' fails,
but query with restriction 'and length(schemavali2_.BINARY_CONTENT)<41180' works normally.
I don't now how to explain this. Though, to reproduce the error you need a 50kb blob probably.
Any suggestions how to trace the error?
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
> Attachments: d3999.sql, log.txt
>
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3999) Can't execute select statement with
blob in network server mode
Posted by "Ashitkin Alexander (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashitkin Alexander updated DERBY-3999:
--------------------------------------
Attachment: log.txt
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
> Attachments: d3999.sql, log.txt
>
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3999) Can't execute select statement with
blob in network server mode
Posted by "Ashitkin Alexander (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashitkin Alexander updated DERBY-3999:
--------------------------------------
Attachment: log.txt
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
> Attachments: d3999.sql, log.txt
>
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3999) Can't execute select statement with
blob in network server mode
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik updated DERBY-3999:
---------------------------------
Derby Categories: [Embedded/Client difference] (was: [Wrong query result, Embedded/Client difference])
Unchecking "wrong query result", since this issue reports a query that fails, not
erroneous data.
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
> Attachments: d3999.sql, log.txt
>
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3999) Can't execute select statement with
blob in network server mode
Posted by "Ashitkin Alexander (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashitkin Alexander updated DERBY-3999:
--------------------------------------
Attachment: (was: log.txt)
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
> Attachments: d3999.sql
>
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-3999) Can't execute select statement with
blob in network server mode
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen resolved DERBY-3999.
---------------------------------------
Resolution: Cannot Reproduce
Setting resolution to "Cannot Reproduce". If someone finds a way to reproduce this, please reopen.
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
> Attachments: d3999.sql, log.txt
>
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3999) Can't execute select statement with
blob in network server mode
Posted by "Ashitkin Alexander (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660089#action_12660089 ]
Ashitkin Alexander commented on DERBY-3999:
-------------------------------------------
yes, i can, but only after holidays - after 3-rd January. Also, as far as i remember, there was no any exception message and nо any useful information in trace. So, i'm not sure i'll find someting useful, but i'll try.
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (DERBY-3999) Can't execute select
statement with blob in network server mode
Posted by "Ashitkin Alexander (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660445#action_12660445 ]
ashitkin.alexander edited comment on DERBY-3999 at 1/3/09 12:37 AM:
--------------------------------------------------------------------
I attached a log. The log isn't very useful because it looks like the derby client logs nothing internally (i use log4j ).
regarding your previous comment - i still can reproduce error, but i investigated an interesting issue:
query with additional restriction 'and length(schemavali2_.BINARY_CONTENT)<41181' fails,
but query with restriction 'and length(schemavali2_.BINARY_CONTENT)<41180' works normally.
I don't know how to explain this. Though, to reproduce the error you need a 50kb blob probably.
Any suggestions how to trace the error?
was (Author: ashitkin.alexander):
I attached a log. The log isn't very useful because it looks like the derby client logs nothing internally (i use log4j ).
regarding your previous comment - i still can reproduce error, but i investigated an interesting issue:
query with additional restriction 'and length(schemavali2_.BINARY_CONTENT)<41181' fails,
but query with restriction 'and length(schemavali2_.BINARY_CONTENT)<41180' works normally.
I don't now how to explain this. Though, to reproduce the error you need a 50kb blob probably.
Any suggestions how to trace the error?
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
> Attachments: d3999.sql, log.txt
>
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3999) Can't execute select statement with
blob in network server mode
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660623#action_12660623 ]
Kristian Waagan commented on DERBY-3999:
----------------------------------------
Thank you.
Then I suggest we try to create a repro for the error to debug it. Seems Knut Anders has already made a good starting point, and hopefully it can be adjusted to trigger the error. It might be related to the DRDA protocol (off-by-one bug?).
Btw, I don't think Derby looks at the environment variables (i.e. set using 'set' or 'export'), but setting them on the JVM command line should do. The derby.properties file can also be used.
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
> Attachments: d3999.sql, log.txt
>
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3999) Can't execute select statement with
blob in network server mode
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12659782#action_12659782 ]
Knut Anders Hatlen commented on DERBY-3999:
-------------------------------------------
Could you also post the stack trace of the EOFException?
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3999) Can't execute select statement with
blob in network server mode
Posted by "Ashitkin Alexander (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660459#action_12660459 ]
Ashitkin Alexander commented on DERBY-3999:
-------------------------------------------
i had tried to set environment variable before server startup:
"set derby.stream.error.logSeverityLevel=0"
and to add jvm parameter in server startup script:
"-Dderby.stream.error.logSeverityLevel=0"
- but nothing changed. the derby.log the same - no any the error related message.
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
> Attachments: d3999.sql, log.txt
>
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3999) Can't execute select statement with
blob in network server mode
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660453#action_12660453 ]
Kristian Waagan commented on DERBY-3999:
----------------------------------------
Are there any error messages in the log file 'derby.log' on the server side?
You could also try to set 'derby.stream.error.logSeverityLevel=0' (restart the server), reproduce the error and then re-check the log file (on the server).
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
> Attachments: d3999.sql, log.txt
>
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3999) Can't execute select statement with
blob in network server mode
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-3999:
--------------------------------------
Attachment: d3999.sql
I made a quick attempt on reproducing the exception with the attached script (d3999.sql) which creates the tables and inserts a couple of rows in each of them before the query is executed, but I didn't see any errors. It would be of great help if you could make the necessary changes to the script so that it reproduces the error, or if you post the exact steps needed to trigger the error.
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
> Attachments: d3999.sql
>
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3999) Can't execute select statement with
blob in network server mode
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706658#action_12706658 ]
Kathey Marsden commented on DERBY-3999:
---------------------------------------
Was there any luck getting a script or java program to reproduce this issue? If not I suggest we close cannot reproduce and then can reopen if a reproduction is discovered.
> Can't execute select statement with blob in network server mode
> ----------------------------------------------------------------
>
> Key: DERBY-3999
> URL: https://issues.apache.org/jira/browse/DERBY-3999
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.4.2.0
> Environment: OS - windows xp, Derby - 10.4.2, client jdbc Driver - org.apache.derby.jdbc.ClientDriver()
> Reporter: Ashitkin Alexander
> Priority: Minor
> Attachments: d3999.sql, log.txt
>
>
> When Derby Derby in ServerMode this query raise the java.io.EOFException(in embedded works normally):
> SELECT
> this_.ID as ID11_2_,
> this_.PROTOCOL_ID as PROTOCOL2_11_2_,
> this_.PROTOCOL_NAME as PROTOCOL3_11_2_,
> this_.PROTOCOL_VERSION as PROTOCOL4_11_2_,
> this_.STORAGE as STORAGE11_2_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_4_,
> schemavali2_.ID as ID4_,
> schemavali2_.ID as ID12_0_,
> schemavali2_.BINARY_CONTENT as BINARY2_12_0_, -- this should be commented to allow normal query execution
> schemavali2_.FILE_NAME as FILE3_12_0_,
> schemavali2_.PROTOCOL_VALIDATION_ID as PROTOCOL4_12_0_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_5_,
> validation3_.ID as ID5_,
> validation3_.ID as ID13_1_,
> validation3_.IS_IMPORTED as IS2_13_1_,
> validation3_.IMPORTED_FILE_NAME as IMPORTED3_13_1_,
> validation3_.ITEM_TEXT as ITEM4_13_1_,
> validation3_.PROPERTY_NAME as PROPERTY5_13_1_,
> validation3_.RULE_NAME as RULE6_13_1_,
> validation3_.SCHEMA_VALIDATION_ID as SCHEMA8_13_1_,
> validation3_.ISSUE_STATUS as ISSUE7_13_1_
> FROM
> VL_PROTOCOL_VALIDATION this_
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION schemavali2_
> ON
> this_.ID=schemavali2_.PROTOCOL_VALIDATION_ID
> LEFT OUTER JOIN
> VL_SCHEMA_VALIDATION_ISSUE validation3_
> ON
> schemavali2_.ID=validation3_.SCHEMA_VALIDATION_ID
> WHERE
> this_.PROTOCOL_NAME='base'
> Tables ddl:
> create table VL_PROTOCOL_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_ID integer,
> PROTOCOL_NAME varchar(100),
> PROTOCOL_VERSION varchar(100),
> STORAGE varchar(20)
> );
> create table VL_SCHEMA_VALIDATION (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> PROTOCOL_VALIDATION_ID integer not null references VL_PROTOCOL_VALIDATION(ID),
> FILE_NAME varchar(250),
> BINARY_CONTENT blob
> );
> create table VL_SCHEMA_VALIDATION_ISSUE (
> ID integer generated always as identity(start with 1, increment by 1) primary key,
> SCHEMA_VALIDATION_ID integer not null references VL_SCHEMA_VALIDATION(ID),
> ITEM_TEXT varchar(1000),
> RULE_NAME varchar(100),
> ISSUE_STATUS varchar(10),
> PROPERTY_NAME varchar(100),
> IS_IMPORTED varchar(10),
> IMPORTED_FILE_NAME varchar(250)
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.