[
https://issues.apache.org/jira/browse/DERBY-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510892
]
Myrna van Lunteren commented on DERBY-1610:
---
thx for your input...Except of course that in some of the
[
https://issues.apache.org/jira/browse/DERBY-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510849
]
Daniel John Debrunner commented on DERBY-1610:
--
It takes a while with that release note to understand
[
https://issues.apache.org/jira/browse/DERBY-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499358
]
Myrna van Lunteren commented on DERBY-1610:
---
Hi,
This issue is one of several that is in progress,
[
https://issues.apache.org/jira/browse/DERBY-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499381
]
Tomohito Nakayama commented on DERBY-1610:
--
I have no objection for your plan on the whole.
I think we
[
https://issues.apache.org/jira/browse/DERBY-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499382
]
Tomohito Nakayama commented on DERBY-1610:
--
Not close but resolve .
Resolve difference of type
[
https://issues.apache.org/jira/browse/DERBY-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496603
]
Rick Hillegas commented on DERBY-1610:
--
Hi Tomohito and Knut Anders,
Is this issue ready to have a release
[
https://issues.apache.org/jira/browse/DERBY-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496619
]
Tomohito Nakayama commented on DERBY-1610:
--
Hi.
I think release note should be written.
However I have a
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12441374 ]
Knut Anders Hatlen commented on DERBY-1610:
---
Thanks Tomohito. If the methods are static, each setter method must
call getColumnMetaDataX(),
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12441400 ]
Tomohito Nakayama commented on DERBY-1610:
--
I see.
It would be a descision.
My stand point is +0.
Resolve difference of type compatibility between
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12441109 ]
Knut Anders Hatlen commented on DERBY-1610:
---
There are some failures in the jdbc40 suite caused by these changes. I'll post
a patch for it.
Resolve
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12441136 ]
Tomohito Nakayama commented on DERBY-1610:
--
Thank you for clean up those.
I have a concern for checkTypeForSetAsciiStream, checkTypeForSetBlob,
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440832 ]
Tomohito Nakayama commented on DERBY-1610:
--
Committed.
Sendingjava/client/org/apache/derby/client/am/PreparedStatement.java
Transmitting file
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440735 ]
Tomohito Nakayama commented on DERBY-1610:
--
Committed.
Sendingjava/client/org/apache/derby/client/am/PreparedStatement.java
Transmitting file
Well This modification may be unneccesary because next 10.3 does
not supoprt jdk13 ...
However, the phenomena was so critical that any set method is failed
on jdk13
I thought it is too sudden change and difficulty for escaping it is
acceptable.
Then I committed ...
Best
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440806 ]
Tomohito Nakayama commented on DERBY-1610:
--
Reading the code, I found problem in the DERBY-1610_7_regressionfix_2_2.patch
...
In the case
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440655 ]
Tomohito Nakayama commented on DERBY-1610:
--
Committed.
Sendingjava/client/org/apache/derby/client/am/PreparedStatement.java
Sending
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440667 ]
Øystein Grøvlen commented on DERBY-1610:
The latest check-in seems to have introduced an error in callable.java
Resolve difference of type compatibility
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440668 ]
Øystein Grøvlen commented on DERBY-1610:
Diff from the tinderbox test:
* Diff file derbyall/derbynetmats/DerbyNet/derbynetmats/callable.diff
***
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440671 ]
Tomohito Nakayama commented on DERBY-1610:
--
Sorry for the regression
I updated next 2 callable.out file in patch.
[EMAIL
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440675 ]
Tomohito Nakayama commented on DERBY-1610:
--
I committed.
Sending
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440677 ]
Tomohito Nakayama commented on DERBY-1610:
--
In addition to the derbyall test, the compatibility test seems to be failed
after this patch.
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440684 ]
Tomohito Nakayama commented on DERBY-1610:
--
I think I could find reason for compatibility error
Next error was found in
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440685 ]
Tomohito Nakayama commented on DERBY-1610:
--
Reading the code, I think I can use org.apache.derby.client.am.ColumnMetaData
instead of ParameterMetadata.
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440687 ]
Tomohito Nakayama commented on DERBY-1610:
--
And compatibility test also
Resolve difference of type compatibility between Embedded and
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440688 ]
Bryan Pendleton commented on DERBY-1610:
It appears that you are working on making this change compatible with JDK 1.3.
I thought we had decided that the
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440716 ]
Tomohito Nakayama commented on DERBY-1610:
--
At least, current lateest release support JDK1.3.
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440717 ]
Bryan Pendleton commented on DERBY-1610:
Here's a link to the 1.3 discussion on the mailing list:
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440719 ]
Tomohito Nakayama commented on DERBY-1610:
--
With the patch DERBY-1610_7_regressionfix_2.patch ,
I executed derbyall and compatibility suite.
The result
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12440726 ]
Tomohito Nakayama commented on DERBY-1610:
--
I think it is possible to solve problem found in jdbcapi/StmtCloseFunTest.java
...
I will post the patch
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12439477 ]
Knut Anders Hatlen commented on DERBY-1610:
---
I have run tests of setNull() and setObject() on most type combinations, and I
didn't find any
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12439485 ]
Tomohito Nakayama commented on DERBY-1610:
--
Thank you for your persistent follow-up !
I will commit the patch after 10.2 is released.
This patch have
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12439547 ]
Bryan Pendleton commented on DERBY-1610:
Is this issue related to the issue discussed in DERBY-1904, specifically:
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12438972 ]
Tomohito Nakayama commented on DERBY-1610:
--
I found another problem in derbynet/csPrepStmt.java.
The part of setNull in this test expect it possible to
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12438886 ]
Tomohito Nakayama commented on DERBY-1610:
--
1)-4)
Test on parameter of type CHAR FOR BIT DATA/VARCHAR FOR BIT DATA/LONG VARCHAR
FOR BIT DATA was not
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12438887 ]
Tomohito Nakayama commented on DERBY-1610:
--
Sorry. I took mistaken.
Test for CHAR FOR BIT DATA/VARCHAR FOR BIT DATA/LONG VARCHAR FOR BIT DATA
existed in
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12438889 ]
Tomohito Nakayama commented on DERBY-1610:
--
In the parameterMapping.java, tests of setNull on parameter typed VARCHAR FOR
BIT DATA (Types.VARBINARY)
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12438952 ]
Tomohito Nakayama commented on DERBY-1610:
--
Regarding 1. setNull(LONGVARCHAR) on parameter of type CHAR FOR BIT DATA
(Types.BINARY): Client succeeds,
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12438657 ]
Knut Anders Hatlen commented on DERBY-1610:
---
Hi Tomohito,
I tried to test all type combinations on setNull(). Seems like most of the
combinations are
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12437796 ]
Tomohito Nakayama commented on DERBY-1610:
--
I found another inconsistency.
At Line 300 in derbynet/callable.java, BLOB is set to variable typed as
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436793 ]
Knut Anders Hatlen commented on DERBY-1610:
---
I'm sorry, I didn't notice the FOR BIT DATA part. I agree with your first
comment, that csPrepStmt should
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436883 ]
Tomohito Nakayama commented on DERBY-1610:
--
Thank you for your concern, Knut.
I will correct csPrepStmt.java and
unify the behavior of
Tomohito Nakayama (JIRA) derby-dev@db.apache.org writes:
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436883
]
Tomohito Nakayama commented on DERBY-1610:
--
Thank you for your concern, Knut.
I will
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436536 ]
Tomohito Nakayama commented on DERBY-1610:
--
I found problem in test of setNull method in derbynet/csPrepStmt.java.
In that test, 16 th value in sql is
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436543 ]
Knut Anders Hatlen commented on DERBY-1610:
---
I'm not sure the test should be changed. The test intentionally calls setNull()
with another type and
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436554 ]
Tomohito Nakayama commented on DERBY-1610:
--
Through examing result, I found another problem, in result of
parameterMapping.java at engine itself.
The
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436555 ]
Tomohito Nakayama commented on DERBY-1610:
--
I correct my previous comment in
http://issues.apache.org/jira/browse/DERBY-1610#action_12436536.
In that
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436557 ]
Tomohito Nakayama commented on DERBY-1610:
--
I understand Knut's comment at
http://issues.apache.org/jira/browse/DERBY-1610#action_12436543.
I found
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436566 ]
Tomohito Nakayama commented on DERBY-1610:
--
Based on Knut's comment at
http://issues.apache.org/jira/browse/DERBY-1610#action_12436543,
The result of
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436568 ]
Tomohito Nakayama commented on DERBY-1610:
--
As I could understand .
Now, we have two inconsistency.
1: Inconsistency in a result of
Hello.
I summarized problems that I encountered through DERBY-1610 in the
comment just before.
I will DERBY-1610.wait() for your response.
Please DERBY-1610.notify() to wake up me.
// It's midnight now in Japan :)
Best regards.
Tomohito Nakayama (JIRA) wrote:
[
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436122 ]
Knut Anders Hatlen commented on DERBY-1610:
---
Although embedded throws XCL12 in some cases, I don't think the client driver
needs to do the same. From
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436209 ]
Tomohito Nakayama commented on DERBY-1610:
--
Thank you for your reviewing.
I tried derbyall last night and found several error happens.
I will submit next
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12435783 ]
Tomohito Nakayama commented on DERBY-1610:
--
I found same problem in VARBINARY as in
http://issues.apache.org/jira/browse/DERBY-1610#action_12435413...
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12434120 ]
Tomohito Nakayama commented on DERBY-1610:
--
Hello.
1)
The jdbcapi/parameterMapping.java takes both of XCL12 and 22005 as expected
Exception...
Well ..
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12434234 ]
Knut Anders Hatlen commented on DERBY-1610:
---
Thank you for the explanation and the new patch, Tomohito!
Since the constant arrays are required to be
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12433196 ]
Knut Anders Hatlen commented on DERBY-1610:
---
Hi Tomohito,
Thank you for working on this issue! I have only had a brief look at your
patch. It looks
Hello.
I understood your suggestion that SQLState 22005 is not equal to just a
error of get method,
though there exists some message problem when setNull throws Exception
for it.
Thank you.
Knut Anders Hatlen (JIRA) wrote:
[
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12431576 ]
Tomohito Nakayama commented on DERBY-1610:
--
Reading the org.apache.derby.client.am.PreparedStatement,
I think each settype name and setNull method should
58 matches
Mail list logo