[jira] Updated: (DERBY-2363) Add initial handshake on connection setup to determine server's required ssl support level and avoid client side attribute settings.

[ https://issues.apache.org/jira/browse/DERBY-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernt M. Johnsen updated DERBY-2363: Fix Version/s: 10.3.0.0 Add initial handshake on connection setup to determine server's

[jira] Updated: (DERBY-2356) Make SSL server authentication optional

[ https://issues.apache.org/jira/browse/DERBY-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernt M. Johnsen updated DERBY-2356: Attachment: derby-2356-v3.diff Uploaded v3. Small change from v2: Avoid creating a new

Multiple simultaneous test runs on the same machine

In the old test harness with the old tests this was impossible due to hardcoded use of port numbers (1527 etc). Is this taken into consideration when tests are moved to JUnit so that the port number(s) may be parameterized in a convenient way? -- Bernt Marius Johnsen, Database Technology Group,

[jira] Commented: (DERBY-2363) Add initial handshake on connection setup to determine server's required ssl support level and avoid client side attribute settings.

[ https://issues.apache.org/jira/browse/DERBY-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475864 ] Bernt M. Johnsen commented on DERBY-2363: - Negotiating SSL/vs plaintext will give a higher latency in calls

Re: Multiple simultaneous test runs on the same machine

Hi Bernt, I have not tried this out but it looks like the port number is configurable by setting a system property. I think that the tricky bits are in org.apache.derbyTesting.junit.TestConfiguration. Hope this helps, -Rick Bernt M. Johnsen wrote: In the old test harness with the old tests

derby faces

Thanks again to Rick Cattell for snapping photos at the Bay Area Derby lunch earlier this month. I have put some of those photos on a wiki page: http://wiki.apache.org/db-derby/DerbyFaces Regards, -Rick

[jira] Subscription: Derby: JIRA issues with patch available

Issue Subscription Filter: Derby: JIRA issues with patch available (19 issues) Subscriber: derby-dev Key Summary DERBY-2371 Setting a default value for a VARCHAR column fails when column contains data https://issues.apache.org/jira/browse/DERBY-2371 DERBY-908

Re: testing javadoc

Also realized in the meantime that the next javadoc build that will be synced to the website will be Monday evening PST, early morning Norway-time, and should include the jdbc4 test suite in the javadoc. Great! Thanks, Andrew :) Dag Andrew McIntyre [EMAIL PROTECTED] writes: On 2/23/07,

no protection of db boot - intended?

Working on DERBY-2264, I notice (again) that booting a database is not protected in any way. Currently, even when authentication (derby.connection.requireAuthentication) is turned on, any user can leave the database in a booted state: If not already booted, the database potentially needs to be

Re: [jira] Commented: (DERBY-47) Some possible improvements to IN optimization

A B (JIRA) wrote: A B commented on DERBY-47: -- Thank you very much for your excellent questions, Mike. My attempted answers are below... Hi Mike, Just wondering if you had any additional questions/inquiries regarding my previous responses to your comments? If

Regression Test Report - Daily 511550 - Sun DBTG

[Auto-generated mail] *Daily* 511550/2007-02-25 18:00:11 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 1430429 089.34% derbyall 068176817 0 357.42% suitesAll sles 0

[jira] Commented: (DERBY-2371) Setting a default value for a VARCHAR column fails when column contains data

[ https://issues.apache.org/jira/browse/DERBY-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475893 ] Bryan Pendleton commented on DERBY-2371: Thanks Saurabh! I intend to commit this patch to the trunk in the

broken network startup scripts

The network startup scripts are broken now, as a result of the work I am doing on DERBY-2196. We decided that, to avoid giving customers a false sense of security, the secure-by-default server should fail to come up if the customer does not specify how they want to authenticate users. Now when

Re: dita 1.3.1 (no asl?) and fop.93

Andrew McIntyre wrote: On 2/2/07, scott hutinger [EMAIL PROTECTED] wrote: I think the important thing, is to move over to fop.93 if possible. I've just attached a patch to DERBY-2373 that allows an upgrade to FOP 0.93. I would appreciate it if any doc builders out there would some spare time

Re: derby faces

Rick Hillegas wrote: Thanks again to Rick Cattell for snapping photos at the Bay Area Derby lunch earlier this month. I have put some of those photos on a wiki page: http://wiki.apache.org/db-derby/DerbyFaces cool! thanks for posting these. it's fun to put faces with names. -jean

[jira] Resolved: (DERBY-2356) Make SSL server authentication optional

[ https://issues.apache.org/jira/browse/DERBY-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernt M. Johnsen resolved DERBY-2356. - Resolution: Fixed Committed revision 511785. Make SSL server authentication optional

Re: Multiple simultaneous test runs on the same machine

On 2/26/07, Bernt M. Johnsen [EMAIL PROTECTED] wrote: In the old test harness with the old tests this was impossible due to hardcoded use of port numbers (1527 etc). Is this taken into consideration when tests are moved to JUnit so that the port number(s) may be parameterized in a convenient

failed to build docs with JDK1.5 and JDK1.6

This may be a known issue?; I had to revert to JDK1.4.2 to build the docs successfully (trunk at revision 511944). Dag Under JDK1.5 I got this error: topicpull: [xslt] Transforming into /home/dw136774/derby/docs/trunk/temp [xslt] Processing

[jira] Commented: (DERBY-2363) Add initial handshake on connection setup to determine server's required ssl support level and avoid client side attribute settings.

[ https://issues.apache.org/jira/browse/DERBY-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475956 ] Bernt M. Johnsen commented on DERBY-2363: - Experimenting with this feature, I find that if a client to do an

Re: failed to build docs with JDK1.5 and JDK1.6

On 2/26/07, Dag H. Wanvik [EMAIL PROTECTED] wrote: This may be a known issue?; I had to revert to JDK1.4.2 to build the docs successfully (trunk at revision 511944). Under JDK1.5 I got this error: /home/dw136774/derby/docs/trunk/DITA-OT1.1.2.1/pretargets.xml:136:

Re: broken network startup scripts

On 2/26/07, Rick Hillegas [EMAIL PROTECTED] wrote: The network startup scripts are broken now, as a result of the work I am doing on DERBY-2196. We decided that, to avoid giving customers a false sense of security, the secure-by-default server should fail to come up if the customer does not

[jira] Commented: (DERBY-378) support for import/export of tables with clob/blob and the other binary data types will be good addition to derby,

[ https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475979 ] Suresh Thalamati commented on DERBY-378: Each blob/clob goes into its own separate external file? Or all the

[jira] Commented: (DERBY-2324) convert StmtCloseFunTest to JUnit

[ https://issues.apache.org/jira/browse/DERBY-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476006 ] Myrna van Lunteren commented on DERBY-2324: --- I think this test can be removed, yes. StmtCloseFunTest is no

[jira] Commented: (DERBY-2371) Setting a default value for a VARCHAR column fails when column contains data

[ https://issues.apache.org/jira/browse/DERBY-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476008 ] Bryan Pendleton commented on DERBY-2371: Committed to the trunk as revision 512019. Will merge to 10.2 now.

[jira] Commented: (DERBY-378) support for import/export of tables with clob/blob and the other binary data types will be good addition to derby,

[ https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476009 ] A B commented on DERBY-378: --- I haven't actually reviewed the code at all, but I was just wondering about the names for the

[jira] Commented: (DERBY-716) Re-enable VTIs

[ https://issues.apache.org/jira/browse/DERBY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476013 ] Rick Hillegas commented on DERBY-716: - Thanks for helping work through the details here. You are, of course,

[jira] Commented: (DERBY-1620) SQL CASE statement returns ERROR 42X89 when including NULL as a return value

[ https://issues.apache.org/jira/browse/DERBY-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476034 ] A B commented on DERBY-1620: John Peterson I will provide more extensive tests and their results shortly John, are

Re: [jira] Commented: (DERBY-47) Some possible improvements to IN optimization

please go ahead with your patch - I think the changes are good incremental steps. The approach with using the flag and code reuse seems reasonable. I am interested in the costing but I think that is separate from the work you are doing. What you have implemented seems in line with the current

[jira] Reopened: (DERBY-2366) Tests DerbyNetNewServer and SecureServerTest fails on weme 6.1

[ https://issues.apache.org/jira/browse/DERBY-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden reopened DERBY-2366: --- Test still fails as described by Rajesh as of 10.3.0.0 alpha - (511195) Tests

[jira] Updated: (DERBY-47) Some possible improvements to IN optimization

[ https://issues.apache.org/jira/browse/DERBY-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B updated DERBY-47: - Attachment: d47_mp_CBO_MoAP_v1.stat d47_mp_CBO_MoAP_v1.patch Committed d47_relOpPredCheck_v1.patch with

[jira] Updated: (DERBY-47) Some possible improvements to IN optimization

[ https://issues.apache.org/jira/browse/DERBY-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B updated DERBY-47: - Derby Info: [Patch Available] Some possible improvements to IN optimization

[jira] Updated: (DERBY-2311) Generate the txt and blobs required for the system tests dynamically

[ https://issues.apache.org/jira/browse/DERBY-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjula Kutty updated DERBY-2311: - Attachment: DERBY-2313_diff.txt DERBY-2311_stat.txt Please find the attached

[jira] Commented: (DERBY-378) support for import/export of tables with clob/blob and the other binary data types will be good addition to derby,

[ https://issues.apache.org/jira/browse/DERBY-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476056 ] Suresh Thalamati commented on DERBY-378: Committed derby_378.diff to trunk on revision 512109. If there

[IP CLEARANCE] IBM contribution of Network Server system tests to Apache Derby

IBM has contributed system tests to Apache Derby: - The ASF secretary recorded the software grant in cclas.txt. - The code was uploaded to Jira issue DERBY-2248. [1] - The ip clearance form was added to the Incubator site. [2] - The Derby vote to accept the contribution passed. [3] If there

Regression Test Report - tinderbox_trunk16 512129 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 512129/2007-02-27 05:12:25 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 2430428 0 110.75% derbyall 068176817 0