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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2007/09/07 23:20:30 UTC
[jira] Resolved: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
[ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-3038.
-----------------------------------
Resolution: Cannot Reproduce
Closing this issue Cannot Reproduce. Please reopen if you get a reproduction for this problem.
> 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: Tools
> 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
> Attachments: create_table.txt, lst_pays.csv, stacktrace.txt, sysinfo.txt, Test3038.java
>
>
> 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.
Re: [jira] Resolved: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by Kathey Marsden <km...@sbcglobal.net>.
Kristian Waagan wrote:
> Kathey Marsden (JIRA) skrev:
>> [
>> https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Kathey Marsden resolved DERBY-3038.
>> -----------------------------------
>>
>> Resolution: Cannot Reproduce
>>
>> Closing this issue Cannot Reproduce. Please reopen if you get a
>> reproduction for this problem.
> Hello Kathey,
>
> You say you are closing the issue, but it is only marked as resolved.
> Is this intentional, or can the issue be marked as closed as well?
>
> As a general note, I believe one can specify the resolution from the
> "Close" screen/dialog. Saves one message and a few clicks :)
> I am aware that mostly marking an issue resolved and closed will be
> carried out by different persons and thus done in two steps.
>
I think I will leave to the reporter EDAH-TALLY to close it especially
since it was filed as a regression. Perhaps EDAH will be able to reopen
it with a repro or perhaps is satisfied with the Cannot Reproduce
status. I think it would be too presumptuous of me to close it. Thanks
for the tip on the single step resolve/close. I will certainly use that
on issues that I file myself.
Kathey
Re: [jira] Resolved: (DERBY-3038) SYSCS_IMPORT_TABLE FAILS : 10.3.1.4
regression ?
Posted by Kristian Waagan <Kr...@Sun.COM>.
Kathey Marsden (JIRA) skrev:
> [ https://issues.apache.org/jira/browse/DERBY-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Kathey Marsden resolved DERBY-3038.
> -----------------------------------
>
> Resolution: Cannot Reproduce
>
> Closing this issue Cannot Reproduce. Please reopen if you get a reproduction for this problem.
>
Hello Kathey,
You say you are closing the issue, but it is only marked as resolved.
Is this intentional, or can the issue be marked as closed as well?
As a general note, I believe one can specify the resolution from the
"Close" screen/dialog. Saves one message and a few clicks :)
I am aware that mostly marking an issue resolved and closed will be
carried out by different persons and thus done in two steps.
regards,
--
Kristian
>
>> 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: Tools
>> 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
>> Attachments: create_table.txt, lst_pays.csv, stacktrace.txt, sysinfo.txt, Test3038.java
>>
>>
>> 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.
>>
>
>