db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "EDAH-TALLY (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4 regression ?
Date Sun, 02 Sep 2007 08:07:19 GMT
SYSCS_IMPORT_TABLE FAILS : 10.3.1.4 regression ?
------------------------------------------------

                 Key: DERBY-3038
                 URL: https://issues.apache.org/jira/browse/DERBY-3038
             Project: Derby
          Issue Type: Bug
          Components: JDBC, Regression Test Failure, Services, SQL
    Affects Versions: 10.3.1.4
         Environment: Linux 2.6.21.1 #2 Tue Jun 26 23:24:34 CEST 2007 i686 AMD Athlon(tm)
XP 2800+ GNU/Linux (Mandriva 2007 Spring)
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
            Reporter: EDAH-TALLY


I used to import data with CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE procedure with 
success in JAVA and DERBY 10.2.2.0.

Since 10.3.1.4, the import procedure fails.

The error message is : 
The exception 'java.sql.SQLException: No current connection.' was thrown while 
evaluating an expression.

I'm sure there is a connection, the same which created the statement : 
***************************************************************************************************
    protected boolean importTableDataCOUNTRIES() {
        try {
            java.sql.Statement st = 
conn.createStatement(java.sql.ResultSet.TYPE_SCROLL_INSENSITIVE, 
java.sql.ResultSet.CONCUR_UPDATABLE);
            String sql = "";

            sql = "CALL 
SYSCS_UTIL.SYSCS_IMPORT_TABLE('NMSET', 'PAYS', '/tmp/lst_pays.csv', 
null, null, null, 1)";
            st.executeUpdate(sql);
            
            return true;
        } catch (SQLException ex) {
            debug(ex.getMessage());
        }
        return false;
    }
***************************************************************************************************
The database is not being accessed by another application. The table does 
exist. The CSV file is comma separated and strings are enclosed by ".

Thank you for considering this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message