[
http://issues.apache.org/jira/browse/DERBY-1633?page=comments#action_12431277 ]
A B commented on DERBY-1633:
----------------------------
> Our application is too network-server centric to run in embedded mode.
Actually, you wouldn't need to change your application at all. You have the
database and you have the query. So if you have a full set of Derby jars (ex.
the 10.2 beta jars), you could just put the query into a file and execute it
directly using Derby's "ij" tool.
Ex. Create a file called "mySQLFile.sql" with contents as follows:
<begin contents>
-- The following URL is for the embedded driver
connect 'jdbc:derby:TPCDB';
set schema tpc;
elapsedtime on;
prepare qFail as '
SELECT DISTINCT
ZONE.ZONE_ID ZONE_ID,
PORT.PORT_ID PORT_ID,
ENTITY_TO_PORT.TYPE,
ENTITY_TO_PORT.PREFIX_ID,
ENTITY_TO_PORT.ENTITY_ID,
ENTITY_TO_PORT.DISPLAY_NAME,
ENTITY_TO_PORT.PORT_DISPLAY_NAME,
PORT2ZONE.MEMBER_NAME,
PORT2ZONE.ZONE_MEMBER_ID,
PORT.PORT_NUMBER
FROM
T_RES_ZONE ZONE
left outer join
T_VIEW_PORT2ZONE PORT2ZONE
on
ZONE.ZONE_ID = PORT2ZONE.ZONE_ID
left outer join
T_RES_PORT PORT
on
PORT2ZONE.PORT_ID = PORT.PORT_ID
left outer join
T_VIEW_ENTITY_TO_PORT ENTITY_TO_PORT
on
PORT2ZONE.PORT_ID = ENTITY_TO_PORT.PORT_ID and
PORT2ZONE.ZONE_ID = ENTITY_TO_PORT.ZONE_ID,
T_RES_FABRIC FABRIC
WHERE
PORT2ZONE.ZONE_ID = ZONE.ZONE_ID and
ZONE.FABRIC_WWN = FABRIC.FABRIC_WWN and
FABRIC.FABRIC_ID = 1
';
execute qFail;
<end contents>
Then do:
> java org.apache.derby.tools.ij
ij> run 'mySQLFile.sql';
That should be all you need to do. But I see you've filed a separate issue
already, so that's fine :) Thanks for following through...
> Regression: The fields of views are not being calculated properly since
> 10.1.2.4
> --------------------------------------------------------------------------------
>
> Key: DERBY-1633
> URL: http://issues.apache.org/jira/browse/DERBY-1633
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.1.3.0, 10.1.3.1
> Environment: 2.8 GHZ dual PIV on Windows XP SP2, 2 GB memory
> Reporter: Prasenjit Sarkar
> Assigned To: A B
> Fix For: 10.2.1.0, 10.3.0.0, 10.1.3.2
>
> Attachments: d1633_10_1_merge.patch, d1633_repro.sql,
> d1633_v1_reviewOnly.patch, d1633_v2.patch, d1633_v3_code.patch,
> d1633_v3_tests.patch, DERBY-1633_v1.html, DERBY-1633_v2.html,
> DERBY-1633_v3.html
>
>
> Database can be assumed to be same as in Derby - 1205 Jira issue
> SELECT PORT1.PORT_ID FROM T_RES_PORT PORT1, T_VIEW_ENTITY2PORT ENTITY2PORT
> WHERE ENTITY2PORT.PORT_ID = PORT1.PORT_ID
> This works fine in 10.1.2.1 but fails thereafter complaining that Comparison
> between INTEGER and CHAR is not supported
> for some reason, it thinks one of the PORT_ID columns is a character, when in
> reality both are integers.
> SELECT DISTINCT
> ZONE.ZONE_ID ZONE_ID,
> PORT2ZONE.ZONE_MEMBER_ID
> FROM
> T_RES_ZONE ZONE left outer join T_VIEW_PORT2ZONE
> PORT2ZONE on
> ZONE.ZONE_ID = PORT2ZONE.ZONE_ID , T_RES_FABRIC
> FABRIC
> In this query, it is complaining that one of the columns is a VARCHAR and
> cannot be compared to INTEGER, when clearly this is not the case...
> Same issue
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
