[jira] Closed: (DERBY-7) Bug in NULLIF Function

[ http://issues.apache.org/jira/browse/DERBY-7?page=all ] Mamta A. Satoor closed DERBY-7: --- Prior to submitting a patch for this issue, I had gone through all the activities on this issue in JIRA and on Derby mailing list. I don't think any outstanding i

[jira] Commented: (DERBY-882) Increasing size of varchar type using ALTER TABLE can implicitly change the column from NOT NULL to NULLable.

[ http://issues.apache.org/jira/browse/DERBY-882?page=comments#action_12364191 ] Satheesh Bandaram commented on DERBY-882: - I have a patch for this problem. Running tests currently. Will post the patch tomorrow. I would like to submit this patch to

[jira] Created: (DERBY-882) Increasing size of varchar type using ALTER TABLE can implicitly change the column from NOT NULL to NULLable.

Increasing size of varchar type using ALTER TABLE can implicitly change the column from NOT NULL to NULLable. - Key: DERBY-882 URL: http://issues.apache.org/jira/browse/DE

[jira] Assigned: (DERBY-882) Increasing size of varchar type using ALTER TABLE can implicitly change the column from NOT NULL to NULLable.

[ http://issues.apache.org/jira/browse/DERBY-882?page=all ] Satheesh Bandaram reassigned DERBY-882: --- Assign To: Satheesh Bandaram > Increasing size of varchar type using ALTER TABLE can implicitly change the > column from NOT NULL to NULLable. > -

Possible regression from 10.1 to 10.2

Hi , I'm seeing a difference in behaviour of derby from version 10.1 and 10.2. Looks like it is regression. But no idea about the reason.The schema I have used is CREATE TABLE inbox (id bigint generated always as identity (start with 1,increment by 1), date timestamp,

[jira] Commented: (DERBY-869) documentation to address Derby-783

[ http://issues.apache.org/jira/browse/DERBY-869?page=comments#action_12364190 ] Mamta A. Satoor commented on DERBY-869: --- I looked at the last html file submitted by Eric and it looks set to go. Can a committer please commit it? > documentation to ad

[jira] Closed: (DERBY-359) GENERATED BY DEFAULT identity option should consume identity values even if the transaction aborts. This would allow skipping over user inserted values during system generat

[ http://issues.apache.org/jira/browse/DERBY-359?page=all ] Mamta A. Satoor closed DERBY-359: - > GENERATED BY DEFAULT identity option should consume identity values even if > the transaction aborts. This would allow skipping over user inserted values

[jira] Resolved: (DERBY-359) GENERATED BY DEFAULT identity option should consume identity values even if the transaction aborts. This would allow skipping over user inserted values during system gener

[ http://issues.apache.org/jira/browse/DERBY-359?page=all ] Mamta A. Satoor resolved DERBY-359: --- Resolution: Won't Fix The sql script provided for this JIRA entry was run with autocommit off, meaning the DDL and DML were in one single transaction

[jira] Assigned: (DERBY-359) GENERATED BY DEFAULT identity option should consume identity values even if the transaction aborts. This would allow skipping over user inserted values during system gener

[ http://issues.apache.org/jira/browse/DERBY-359?page=all ] Mamta A. Satoor reassigned DERBY-359: - Assign To: Mamta A. Satoor > GENERATED BY DEFAULT identity option should consume identity values even if > the transaction aborts. This would allow sk

[jira] Commented: (DERBY-855) Document optimizer overrides which were introduced in 10.2

[ http://issues.apache.org/jira/browse/DERBY-855?page=comments#action_12364181 ] Mamta A. Satoor commented on DERBY-855: --- Following are examples of the 4 optimizer overrides 1)constraint CREATE TABLE t1 (c1 int, c2 int, c3 int, CONSTRAINT cons1 PRIMARY

Re: Server and client compatibility test for 10.2 and 10.1

Ramandeep Kaur wrote: >Thanks to Kathey for proposed solution. > >1. As per task 1, I have opened JIRA issues for failed tests:- >http://issues.apache.org/jira/browse/DERBY-880 >http://issues.apache.org/jira/browse/DERBY-881 > > Thank you Raman for doing this testing, finding these issues, and l

Re: Server and client compatibility test for 10.2 and 10.1

Kathey Marsden wrote: > Myrna van Lunteren wrote: It occured to me the other day, and maybe this was the intention, that this testing is not limited to network server and clients. I should be able to run java -cp derby10.1/derbyTesting.jar:derby10.2/derby.jar org.apache.derbyTesting.fun

[jira] Updated: (DERBY-747) Derby Logo Work

[ http://issues.apache.org/jira/browse/DERBY-747?page=all ] Jean T. Anderson updated DERBY-747: --- Description: The Derby logo was voted on and a logo selected; see DERBY-297. This Jira issue provides a spot for uploading images for final fine tuning.

[jira] Commented: (DERBY-880) jdbcapi/connectionJdbc20.java fails for server (10.1.2.2) and client (10.2.0.0) compatibility testing

[ http://issues.apache.org/jira/browse/DERBY-880?page=comments#action_12364178 ] Kathey Marsden commented on DERBY-880: -- Looking at the svn log, It looks like this error was added in DERBY-721 r357435 | tmnk | 2005-12-17 21:15:39 -0800 (Sat, 17 Dec 200

[jira] Updated: (DERBY-747) Derby Logo Work

[ http://issues.apache.org/jira/browse/DERBY-747?page=all ] Jean T. Anderson updated DERBY-747: --- Attachment: (was: derby_logo_small_dec21.png) > Derby Logo Work > --- > > Key: DERBY-747 > URL: http://issues.apache.org/

Re: Server and client compatibility test for 10.2 and 10.1

Thanks to Kathey for proposed solution.   1. As per task 1, I have opened JIRA issues for failed tests:- http://issues.apache.org/jira/browse/DERBY-880http://issues.apache.org/jira/browse/DERBY-881   2. I will work on task 2 to skip failing tests while running server and client compatibility testi

Re: Removing Derby tagline

On Wed, 25 Jan 2006 14:58:32, David W. Van Couvering wrote: We are trying to finalize the work on the Derby logo and getting this posted to the web site and other places. The one issue still open is the tagline. We all voted +1 for the images that had the tagline "Pure Java Database." It's

[jira] Updated: (DERBY-881) jdbcapi/LOBTest.java fails for server (10.1.2.2) and client (10.2.0.0) compatibility testing

[ http://issues.apache.org/jira/browse/DERBY-881?page=all ] Ramandeep Kaur updated DERBY-881: - Attachment: LOBTest.diff LOBTest.tmp LOBTest.tmpmstr > jdbcapi/LOBTest.java fails for server (10.1.2.2) and client (10.2.0.0)

[jira] Created: (DERBY-881) jdbcapi/LOBTest.java fails for server (10.1.2.2) and client (10.2.0.0) compatibility testing

jdbcapi/LOBTest.java fails for server (10.1.2.2) and client (10.2.0.0) compatibility testing - Key: DERBY-881 URL: http://issues.apache.org/jira/browse/DERBY-881 Project: Derby

[jira] Updated: (DERBY-880) jdbcapi/connectionJdbc20.java fails for server (10.1.2.2) and client (10.2.0.0) compatibility testing

[ http://issues.apache.org/jira/browse/DERBY-880?page=all ] Ramandeep Kaur updated DERBY-880: - Attachment: connectionJdbc20.diff connectionJdbc20.tmp connectionJdbc20.tmpmstr > jdbcapi/connectionJdbc20.java fails for serv

[jira] Created: (DERBY-880) jdbcapi/connectionJdbc20.java fails for server (10.1.2.2) and client (10.2.0.0) compatibility testing

jdbcapi/connectionJdbc20.java fails for server (10.1.2.2) and client (10.2.0.0) compatibility testing --- Key: DERBY-880 URL: http://issues.apache.org/jira/browse/DERBY-880

[jira] Commented: (DERBY-398) Exclude tests for J2ME/CDC/Foundation platform

[ http://issues.apache.org/jira/browse/DERBY-398?page=comments#action_12364173 ] Kathey Marsden commented on DERBY-398: -- I checked in this parameterMapping_2.diff Date: Thu Jan 26 19:06:10 2006 New Revision: 372708 URL: http://svn.apache.org/viewcvs?r

[jira] Commented: (DERBY-859) Resolve the IBM15 test failures by updating the corresponding master files

[ http://issues.apache.org/jira/browse/DERBY-859?page=comments#action_12364172 ] Andrew McIntyre commented on DERBY-859: --- Hi Manjula, This looks good to me except for the dcl.out output. It looks like the build you used to test with didn't include th

[jira] Updated: (DERBY-809) Incorrect documentation for 'NetworkServerControl.logConnections(boolean)'

[ http://issues.apache.org/jira/browse/DERBY-809?page=all ] Andrew McIntyre updated DERBY-809: -- Fix Version: (was: 10.1.2.2) > Incorrect documentation for 'NetworkServerControl.logConnections(boolean)' > -

[jira] Updated: (DERBY-744) Problem setting sanity state to false by using 'ant -Dsane=false'

[ http://issues.apache.org/jira/browse/DERBY-744?page=all ] Andrew McIntyre updated DERBY-744: -- Fix Version: (was: 10.1.3.0) (was: 10.1.2.2) > Problem setting sanity state to false by using 'ant -Dsane=false' > -

Re: documenting DERBY-571: virtual table mapping for no argument diagnostic tables

Eric Radzinski wrote: > Can somebody tell me if the four tables that are associated with this > issue need to be documented? The tables are: > > SYSCS_DIAG.LOCK_TABLE > SYSCS_DIAG.STATEMENT_CACHE > SYSCS_DIAG.TRANSACTION_TABLE > SYSCS_DIAG.ERROR_MESSAGES > > If so, I'll start putting together

Re: Removing Derby tagline

Andrew McIntyre wrote: On 1/26/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote: ah! one thing is stopping us. The talent to produce that crisp, clean final in several sizes, including a size that works for the web site. Actually, since Roger attached the Illustrator file for the logo and I ha

Re: Removing Derby tagline

Daniel John Debrunner wrote: Jean T. Anderson wrote: Daniel John Debrunner wrote: I disagree. Here is an example of what it would look like to just get the hat up on the web site: I just don't believe that is anything stopping us from doing that: ah! one thing is stopping us. The t

Re: Removing Derby tagline

On 1/26/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote: > > ah! one thing is stopping us. The talent to produce that crisp, clean > final in several sizes, including a size that works for the web site. Actually, since Roger attached the Illustrator file for the logo and I have the font he used (My

Re: Removing Derby tagline

Jean T. Anderson wrote: > Daniel John Debrunner wrote: >>> I disagree. Here is an example of what it would look like to just get >>> the hat up on the web site: >> I just don't believe that is anything stopping us from doing that: >> > ah! one thing is stopping us. The talent to produce that cri

Re: [jira] Commented: (DERBY-879) The Getting Started Guide is incomplete (section: Installing and working with Derby) and so not helpful to new users

On 1/26/06, Bryan Pendleton <[EMAIL PROTECTED]> wrote: > > - improve the bundled scripts to be easier to use > - re-arrange the directory structure to be more obvious (I was > certainly confused by the concept of a "framework" when I first > started with Derby). > - issue better error

Re: Removing Derby tagline

Daniel John Debrunner wrote: Jean T. Anderson wrote: Daniel John Debrunner wrote: ... All but one of the images did not include the tagline with the trademark, so there is nothing stopping us getting some image up on the site. I disagree. Here is an example of what it would look like to

[jira] Closed: (DERBY-783) Enhance ALTER TABLE syntax to allow users to change the next value to be generated for an identity column

[ http://issues.apache.org/jira/browse/DERBY-783?page=all ] Mamta A. Satoor closed DERBY-783: - > Enhance ALTER TABLE syntax to allow users to change the next value to be > generated for an identity column > -

[jira] Resolved: (DERBY-783) Enhance ALTER TABLE syntax to allow users to change the next value to be generated for an identity column

[ http://issues.apache.org/jira/browse/DERBY-783?page=all ] Mamta A. Satoor resolved DERBY-783: --- Fix Version: 10.2.0.0 Resolution: Fixed All the code changes for this are checked in. There is a subtask open for documentation > Enhance ALTER

[jira] Updated: (DERBY-747) Derby Logo Work

[ http://issues.apache.org/jira/browse/DERBY-747?page=all ] Andrew McIntyre updated DERBY-747: -- Attachment: (was: derby-logo-right-align.jpg) > Derby Logo Work > --- > > Key: DERBY-747 > URL: http://issues.apache.org/ji

[jira] Updated: (DERBY-747) Derby Logo Work

[ http://issues.apache.org/jira/browse/DERBY-747?page=all ] Andrew McIntyre updated DERBY-747: -- Attachment: (was: derby-logo-move.jpg) > Derby Logo Work > --- > > Key: DERBY-747 > URL: http://issues.apache.org/jira/brow

Re: Decluttering DERBY-747 "Derby Logo Work"

On 1/26/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote: > > I would recommend that Andrew and Susan remove their variants, > specifically these images: > > https://issues.apache.org/jira/secure/attachment/12321510/derby-logo-move.jpg > https://issues.apache.org/jira/secure/attachment/12321511/derby

Re: Jira patch available option

On 1/26/06, Mamta Satoor <[EMAIL PROTECTED]> wrote: > May be this is asking for too much but is there a check box or anything else > that says patch has been reviewed and there are comments on the patch for > the submitter. > > Mamta We could do this, I suppose, but it might be overkill. It should

[jira] Commented: (DERBY-862) Clean up the big pile of javadoc warnings for the derbydocs target and make derbydocs run under jdk1.6

[ http://issues.apache.org/jira/browse/DERBY-862?page=comments#action_12364162 ] Rick Hillegas commented on DERBY-862: - Hi David, Thanks for looking at this patch. You are right, the uploaded patch file generates an error when I try to apply it to a cl

[jira] Updated: (DERBY-869) documentation to address Derby-783

[ http://issues.apache.org/jira/browse/DERBY-869?page=all ] Eric Radzinski updated DERBY-869: - Attachment: derby869.diff rrefsqlj81859.html All set. I've incorporated your latest comments. Patch and HTML file are included. > documenta

[jira] Updated: (DERBY-879) The Getting Started Guide is incomplete (section: Installing and working with Derby) and so not helpful to new users

[ http://issues.apache.org/jira/browse/DERBY-879?page=all ] Stan Bradbury updated DERBY-879: Comment: was deleted > The Getting Started Guide is incomplete (section: Installing and working with > Derby) and so not helpful to new users >

[jira] Commented: (DERBY-783) Enhance ALTER TABLE syntax to allow users to change the next value to be generated for an identity column

[ http://issues.apache.org/jira/browse/DERBY-783?page=comments#action_12364157 ] Satheesh Bandaram commented on DERBY-783: - New changes submitted to set START value in the catalog to RESTART option of ALTER table is committed. Sending java\

Re: [jira] Commented: (DERBY-879) The Getting Started Guide is incomplete (section: Installing and working with Derby) and so not helpful to new users

Stan Bradbury (JIRA) wrote: The following email prompted the filing of this JIRA entry: = Feedback on the initial Derby experience That is a very interesting set of experiences. It's not obvious to me that all of these are necessarily best fixed via documentation. In some cases, it mi

[jira] Commented: (DERBY-879) The Getting Started Guide is incomplete (section: Installing and working with Derby) and so not helpful to new users

[ http://issues.apache.org/jira/browse/DERBY-879?page=comments#action_12364156 ] Stan Bradbury commented on DERBY-879: - A basic rewrtie of section: " Manually setting environment variables and paths": -- hope you find this useful. Change title to: Sett

[jira] Commented: (DERBY-879) The Getting Started Guide is incomplete (section: Installing and working with Derby) and so not helpful to new users

[ http://issues.apache.org/jira/browse/DERBY-879?page=comments#action_12364154 ] Stan Bradbury commented on DERBY-879: - The following email prompted the filing of this JIRA entry: = Feedback on the initial Derby experience Here are my UCD [User

Re: Removing Derby tagline

Jean T. Anderson wrote: > Daniel John Debrunner wrote: > >> ... All but one of the images did not include the tagline with the >> trademark, so there is nothing stopping us getting some image up on the >> site. > > > I disagree. Here is an example of what it would look like to just get > the ha

[jira] Created: (DERBY-879) The Getting Started Guide is incomplete (section: Installing and working with Derby) and so not helpful to new users

The Getting Started Guide is incomplete (section: Installing and working with Derby) and so not helpful to new users Key: DERBY-879 URL: http://issues.apache.org/

[jira] Updated: (DERBY-783) Enhance ALTER TABLE syntax to allow users to change the next value to be generated for an identity column

[ http://issues.apache.org/jira/browse/DERBY-783?page=all ] Mamta A. Satoor updated DERBY-783: -- Attachment: Derby783AlterTableRestartWith012606.txt Here is the patch (Derby783AlterTableRestartWith012606.txt) with commented code removed. > Enhance ALTE

Bogus diffs through viewcvs

Be wary of looking at changed files through viewcvs. I was just looking at the changes for sqlgrammar.jj from the "Subversion Commits" section of DERBY-783 for 370885. Looking at sqlgrammar.jj, I was very confused how the change had gone in with out any use of . However, the default option of "Un

Re: [jira] Commented: (DERBY-855) Document optimizer overrides which were introduced in 10.2

Hi Eric,   I was busy with a metadata bug so couldn't get back to you sooner. I will post something in the JIRA for this soon.   thanks, Mamta  On 1/26/06, Eric Radzinski (JIRA) wrote:    [ http://issues.apache.org/jira/browse/DERBY-855?page=comments#action_12364115 ]Eric

Re: Jira patch available option

May be this is asking for too much but is there a check box or anything else that says patch has been reviewed and there are comments on the patch for the submitter.   Mamta  On 1/26/06, David W. Van Couvering <[EMAIL PROTECTED]> wrote: That's great!Andrew McIntyre wrote:>> On Jan 26, 2006, at 6:54

[jira] Commented: (DERBY-869) documentation to address Derby-783

[ http://issues.apache.org/jira/browse/DERBY-869?page=comments#action_12364133 ] Mamta A. Satoor commented on DERBY-869: --- Couple of trivial comments 1)At the top of the ALTER TABLE statement page, there are 5 bullet items explaining what alter table s

Re: A few questions about index usage

HI Harri, Allowing reverse scans in Derby  would be a nice enhancement. In addition, the CREATE INDEX statement could be modified to provide the 'ALLOW/DISALLOW REVERSE SCANS'  option  during index creation. You may begin by logging an 'Enhancement' issue in JIRA and proposing/discussing your ide

Re: Jira patch available option

That's great! Andrew McIntyre wrote: On Jan 26, 2006, at 6:54 AM, Daniel John Debrunner wrote: I just entered a Jira bug against Geronimo and saw they have a check-box that says 'Patch Available'. It's in a section called 'Geronimo Info'. This ties in with something I saw in the Forrest Jir

Re: [jira] Commented: (DERBY-866) BUILT-IN Derby User Management (DDL) Enhancements

On 1/26/06, Daniel John Debrunner <[EMAIL PROTECTED]> wrote: > Francois Orsini (JIRA) wrote: > > > [ > > http://issues.apache.org/jira/browse/DERBY-866?page=comments#action_12364090 > > ] > > > > Francois Orsini commented on DERBY-866: > > --- > > > In this

Re: A few questions about index usage

1) "SELECT MIN(Id) FROM Customer" and "SELECT MAX(Id) FROM Customer" are both fast, but "SELECT MIN(Id), MAX(Id) FROM Customer" is slow, taking 5 seconds. Why? Derby knows how to use an index to quickly find a minimum or a maximum (by traversing down one side of the B-tree or the other). It

[jira] Commented: (DERBY-491) Protocol exception when Network Server tries to return ~32K of data or greater in a result set for a Java stored procedure.

[ http://issues.apache.org/jira/browse/DERBY-491?page=comments#action_12364124 ] A B commented on DERBY-491: --- For those wondering, Bryan's latest patch addreses comments I made here: http://article.gmane.org/gmane.comp.apache.db.derby.devel/12818 Thanks as alway

[jira] Updated: (DERBY-491) Protocol exception when Network Server tries to return ~32K of data or greater in a result set for a Java stored procedure.

[ http://issues.apache.org/jira/browse/DERBY-491?page=all ] Bryan Pendleton updated DERBY-491: -- Attachment: svn_jan_26_2006.diff Updated the comments in the regression test to explain the test behavior more clearly and accurately, and to include a poin

[jira] Updated: (DERBY-491) Protocol exception when Network Server tries to return ~32K of data or greater in a result set for a Java stored procedure.

[ http://issues.apache.org/jira/browse/DERBY-491?page=all ] Bryan Pendleton updated DERBY-491: -- Attachment: changes.html > Protocol exception when Network Server tries to return ~32K of data or > greater in a result set for a Java stored procedure. > -

[jira] Updated: (DERBY-491) Protocol exception when Network Server tries to return ~32K of data or greater in a result set for a Java stored procedure.

[ http://issues.apache.org/jira/browse/DERBY-491?page=all ] Bryan Pendleton updated DERBY-491: -- Attachment: (was: changes.html) > Protocol exception when Network Server tries to return ~32K of data or > greater in a result set for a Java stored pro

Re: doc patches waiting for commit

Eric Radzinski wrote: Can somebody take a look at three of the doc patches that I've created over the past week or so and, if there are no problems with them, commit them? The issues that the patches address are: DERBY-701: changes to Java 2 security policy examples DERBY-678: minor change

Re: [jira] Updated: (DERBY-491) Protocol exception when Network Server tries to return ~32K of data or greater in a result set for a Java stored procedure.

Hi Army, I'm really glad that you noticed that the behavior in the regression test didn't match the comments, because it gave me a chance to go back and really cement my understanding of this bug fix. I will update the fix description in the JIRA entry, and I'll also be posting a new patch with

[jira] Commented: (DERBY-855) Document optimizer overrides which were introduced in 10.2

[ http://issues.apache.org/jira/browse/DERBY-855?page=comments#action_12364115 ] Eric Radzinski commented on DERBY-855: -- I have a few outstanding questions about documenting this issue: --I need some help extracting relevant examples from the source t

Re: conflict between Derby API and JDBC 4.0

Daniel John Debrunner wrote: Rick Hillegas wrote: Three months ago, we shelved this topic, promising to return to it later. I would like to reach consensus on this problem now. In a nutshell: JDBC4 introduces new methods whose signatures contain generics. Because of this, DataSo

A few questions about index usage

I have been testing Derby for a few days. I noticed a couple of odd things. Table definition is create table Customer ( Id bigint generated by default as identity primary key, Name varchar(128), Modified timestamp default current_timestamp ) There are no extra indexes, but Id gets a

[jira] Closed: (DERBY-878) documentation to address DERBY-573

[ http://issues.apache.org/jira/browse/DERBY-878?page=all ] Eric Radzinski closed DERBY-878: Resolution: Duplicate closing this issue. It's a duplicate of Derby-855 > documentation to address DERBY-573 > -- > >

[jira] Created: (DERBY-878) documentation to address DERBY-573

documentation to address DERBY-573 -- Key: DERBY-878 URL: http://issues.apache.org/jira/browse/DERBY-878 Project: Derby Type: Sub-task Components: Documentation Versions: 10.0.2.0 Reporter: Eric Radzinski Assigned to:

[jira] Updated: (DERBY-869) documentation to address Derby-783

[ http://issues.apache.org/jira/browse/DERBY-869?page=all ] Andrew McIntyre updated DERBY-869: -- Other Info: [Patch available] > documentation to address Derby-783 > -- > > Key: DERBY-869 > URL: http://is

[jira] Updated: (DERBY-678) derby documentation does not reflect changes to update lock behavior

[ http://issues.apache.org/jira/browse/DERBY-678?page=all ] Andrew McIntyre updated DERBY-678: -- Other Info: [Patch available] > derby documentation does not reflect changes to update lock behavior > --

Re: Jira patch available option

On Jan 26, 2006, at 6:54 AM, Daniel John Debrunner wrote: I just entered a Jira bug against Geronimo and saw they have a check-box that says 'Patch Available'. It's in a section called 'Geronimo Info'. This ties in with something I saw in the Forrest Jira page, a query for open issues wit

[jira] Updated: (DERBY-701) Java 2 security policy file examples don't work -- are missing a needed line

[ http://issues.apache.org/jira/browse/DERBY-701?page=all ] Andrew McIntyre updated DERBY-701: -- Other Info: [Patch available] > Java 2 security policy file examples don't work -- are missing a needed line > --

Re: doc patches waiting for commit

Hi Eric,   I owe a doc patch review for Derby-869 ALTER TABLE syntax change. I was neck deep in a metadata duplicate row problem and was just able to narrow the problem down so everything else got sidetracked. Sorry about that. I will try to review the patch in a day or two.   Mamta  On 1/26/06, E

Re: Removing Derby tagline

Daniel John Debrunner wrote: ... All but one of the images did not include the tagline with the trademark, so there is nothing stopping us getting some image up on the site. I disagree. Here is an example of what it would look like to just get the hat up on the web site: http://issues.apach

(DERBY-655) getImportedKeys returns duplicate rows in some cases

Hi,   I have been looking at Derby-655 getImportedKeys returns duplicate rows in some cases. Deepa reported that one of the databases with just t many tables was returning duplicate rows for DatabaseMetaData.getImportedKeys on a particular table. I was able to work on that database and bring i

doc patches waiting for commit

Can somebody take a look at three of the doc patches that I've created over the past week or so and, if there are no problems with them, commit them?   The issues that the patches address are:   DERBY-701: changes to Java 2 security policy examples DERBY-678: minor change to update lock info

Re: Deployed Derby 10.1.2.1 to Apache repository

Jeremy, did you ever get a chance to look at this? Comments, suggestions? On Jan 5, 2006, at 9:44 AM, Andrew McIntyre wrote: So I finally had the time to figure out how to get maven to deploy the Derby jars to the Apache repository. Could one of the maven folks on the list please inspect

[jira] Assigned: (DERBY-841) Internationalize messages in GetResourceBundleAction to ParameterMetadata in org.apache.derby.client.am

[ http://issues.apache.org/jira/browse/DERBY-841?page=all ] David Van Couvering reassigned DERBY-841: - Assign To: David Van Couvering > Internationalize messages in GetResourceBundleAction to ParameterMetadata in > org.apache.derby.client.am > -

[jira] Commented: (DERBY-862) Clean up the big pile of javadoc warnings for the derbydocs target and make derbydocs run under jdk1.6

[ http://issues.apache.org/jira/browse/DERBY-862?page=comments#action_12364103 ] David Van Couvering commented on DERBY-862: --- I tried applying this patch but it failed: patching file java/tools/org/apache/derby/impl/tools/ij/ij.jj patch: malf

Re: Tagline for Derby

Thursday, January 26, 2006, 5:28:02 PM CET, Jean T. Anderson wrote: >> I noticed the following when repeating Kathey's search query on Google: >> >> * MySQL AB and Postgre SQL are the top two results >> * As far as I can see, neither of them include a tagline in their logo >> images (except "Pow

Re: Removing Derby tagline

David W. Van Couvering wrote: > We are trying to finalize the work on the Derby logo and getting this > posted to the web site and other places. The one issue still open is > the tagline. We all voted +1 for the images that had the tagline "Pure > Java Database." To be precise, only one image h

Re: Features of the JUnit test execution harness

Thanks, Kristian. This is indeed helpful. My takeaway is that our JUnit primer should recommend something like this as the pattern if developers need to move the setup()/teardown() brackets outside a cluster of tests. Regards, -Rick Kristian Waagan wrote: Rick Hillegas wrote: Kristian Waa

Re: [jira] Commented: (DERBY-866) BUILT-IN Derby User Management (DDL) Enhancements

Francois Orsini (JIRA) wrote: > [ > http://issues.apache.org/jira/browse/DERBY-866?page=comments#action_12364090 > ] > > Francois Orsini commented on DERBY-866: > --- > In this case, the password column can just be renamed to something else > (i.e. AUTH

Decluttering DERBY-747 "Derby Logo Work"

Originally I created DERBY-747 for Roger to upload the logos that were voted in. Then in kicking off work for the derby web site I started uploading variants to suggest text to go with the hat. Opinions were raised indicating that the text itself should be considered part of the logo; see: h

Re: Tagline for Derby

John Embretsen wrote: Kathey Marsden wrote: I think no tagline would be fine. I noticed, however, that a Google search for "open source database" did not hit our website in at least the first 10 pages, but did see many other open source database alternatives there. I am guessing that tag

[jira] Commented: (DERBY-866) BUILT-IN Derby User Management (DDL) Enhancements

[ http://issues.apache.org/jira/browse/DERBY-866?page=comments#action_12364090 ] Francois Orsini commented on DERBY-866: --- > Daniel John Debrunner commented on DERBY-866: > - > > I see the argument for DDL, m

Jira patch available option

I just entered a Jira bug against Geronimo and saw they have a check-box that says 'Patch Available'. It's in a section called 'Geronimo Info'. https://issues.apache.org/jira/browse/GERONIMO-1545 You can see if it if you go to edit a GERONIMO issue. This ties in with something I saw in the Forr

Re: [jira] Commented: (DERBY-326) Improve streaming of large objects for network server and client

Hello. Kathey Marsden (JIRA) wrote: I couldn't think of how to get an error on getCharacterStream/getBinaryStream but I wonder, could the work done in openInputStreamLazily() just be part of readInputStreamInitially so that these calls could just throw an SQLException if encountered?

Re: Features of the JUnit test execution harness

I think there's a lot of value in having a suite-level setup mechanism, I totally agree that doing setup for each test can be overkill and I am often finding ways to work around it. David Kristian Waagan wrote: Rick Hillegas wrote: Kristian Waagan wrote: 2) Should we support setting up

Re: [jira] Updated: (DERBY-326) Improve streaming of large objects for network server and client

Hello. I follow myself again TomohitoNakayama wrote: ReEncodedInputStream.java.modifiedForLongRun does not create decoded buffer for each time when reEncode was created. However, encocded buffer is created for each time as before. To escape creating encoded buffer for each time, I thi

[jira] Updated: (DERBY-877) zOS - with DerbyClient getDate(#) fails with IllegalArgumentException - unsupported date format - resultset.java

[ http://issues.apache.org/jira/browse/DERBY-877?page=all ] Myrna van Lunteren updated DERBY-877: - Description: The test lang/resultset.java fails with DerbyNetClient on zOS because ResultSet.getDate(#) fails with an java.lang.IllegalArgumentExcept

[jira] Created: (DERBY-877) zOS - with DerbyClient getDate(#) fails with IllegalArgumentException - unsupported date format - resultset.java

zOS - with DerbyClient getDate(#) fails with IllegalArgumentException - unsupported date format - resultset.java Key: DERBY-877 URL: http://issues.apache.org/jira/bro

[jira] Created: (DERBY-876) DatabaseMetaData.getSchemas() is not JDBC 3.0 compliant

DatabaseMetaData.getSchemas() is not JDBC 3.0 compliant --- Key: DERBY-876 URL: http://issues.apache.org/jira/browse/DERBY-876 Project: Derby Type: Bug Components: JDBC Reporter: Bernt M. Johnsen The resul

Re: [jira] Commented: (DERBY-819) Provide JDBC4 SQLException subclasses support in Embedded driver

Hi, Anurag, this sounds interesting, I generally like this kind of approach over creating hardcoded specific SQLException classes in our code. We should be able to solve this in a way that is less hardcoded and more flexible, which is always good for long-term maintainability. I don't quite

Re: Features of the JUnit test execution harness

Rick Hillegas wrote: Kristian Waagan wrote: 2) Should we support setting up a shared test fixture for a set of tests? This is a common issue with JUnit, and there are mechanisms to handle it. For instance, we could let tests that require this to wrap itself in a TestSetup instance (as d

Re: Tagline for Derby

Kathey Marsden wrote: I think no tagline would be fine. I noticed, however, that a Google search for "open source database" did not hit our website in at least the first 10 pages, but did see many other open source database alternatives there. I am guessing that tag line would add us to t

Re: [jira] Commented: (DERBY-866) BUILT-IN Derby User Management (DDL) Enhancements

On 1/25/06, Daniel John Debrunner <[EMAIL PROTECTED]> wrote: > Francois Orsini (JIRA) wrote: > > [ > > http://issues.apache.org/jira/browse/DERBY-866?page=comments#action_12364050 > > ] > > > > Francois Orsini commented on DERBY-866: > > --- > > > > > >>Dan

Re: [jira] Created: (DERBY-866) BUILT-IN Derby User Management (DDL) Enhancements

On 1/25/06, Satheesh Bandaram <[EMAIL PROTECTED]> wrote: > Thanks for your answers, Francois... Some more below... > > On 1/24/06, Satheesh Bandaram <[EMAIL PROTECTED] > wrote: > > > > > > Why not sure LDAP or some other standard authentication models? It may be > good to strengthen Derby authenti

Re: [jira] Updated: (DERBY-491) Protocol exception when Network Server tries to return ~32K of data or greater in a result set for a Java stored procedure.

Bryan Pendleton wrote (2006-01-25 09:59:42): > >for DERBY-491, I was expecting to see a protocol exception for the first > >test case (DERBY-491), not a hang. > > Interesting. That's my expectation too, so I'm not sure I understand > why the behavior changed. > > Good catch! Let me

Re: Removing Derby tagline

+1 for removing the tagline +1 for putting it back later when Sun figures we can -- Bernt Marius Johnsen, Database Technology Group, Staff Engineer, Technical Lead Derby/Java DB Sun Microsystems, Trondheim, Norway signature.asc Description: Digital signature