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 "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2009/01/01 17:52:44 UTC
[jira] Updated: (DERBY-3999) Can't execute select statement with
blob in network server mode
[ 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.