Re: [jira] Commented: (DERBY-499) Expose BOOLEAN datatype to end users

Rick Hillegas wrote: > > > What if the metadata test internally verified that the version numbers > from the client driver agreed with the values in dnc.properties? Then > we wouldn't have to hard code version numbers anywhere: not in the > test code and not in the canons. We could remove the meta

Re: Incorrect Javadoc for NetworkServerControl.logConnections()?

Kristian Waagan wrote: Hello, While investigating a little around logging of connections, I found that the Javadoc of NetworkServerControl.logConnections(boolean) states that a message is printed to derby.log when a connection is made or closed. I do not observe this when connecting/disconnec

Re: [jira] Commented: (DERBY-499) Expose BOOLEAN datatype to end users

On Jan 11, 2006, at 3:29 PM, Rick Hillegas wrote: Thanks for pointing me at this piece of the release machinery. I have a naive question: If we have this programmatic way of generating new release numbers and then poking them into test canons, what are we testing here? Currently, only th

Re: Message round-trips between Derby client and server

Knut Anders Hatlen wrote: >Bryan Pendleton <[EMAIL PROTECTED]> writes: > > > >>Knut Anders Hatlen wrote: >> >> >>>I haven't been thinking about the details, but at least it seems like >>>this is what PostgreSQL and MySQL do. >>> >>> > >I think I may have jumped to the wrong conclusions

Re: Question about closing connection and statement objects

On 1/11/06, Daniel John Debrunner <[EMAIL PROTECTED]> wrote: > Deepa Remesh wrote: > > Should a JDBC driver close the statement objects associated with a > > connection when the connection's close() method is called? > > > > I saw this in JDBC 3.0 spec (Section 13.1.3 Closing Statement Objects) > >

[jira] Created: (DERBY-808) PreparedStatements can take longer to execute than Statements. There seem to be two problems with searchClauseTransitiveClosure method in PredicateList.java

PreparedStatements can take longer to execute than Statements. There seem to be two problems with searchClauseTransitiveClosure method in PredicateList.java -

Re: [VOTE] Rick Hillegas as a committer

+1 Øyvind (still not productive on Derby, will be getting up to speed at Google for a while...)

Re: derby bay area lunch

Hi, Please count me in. Thanks Manjula Myrna van Lunteren wrote: Hi, Wednesday Feb 1 would work fine for me... Myrna

Re: [jira] Commented: (DERBY-499) Expose BOOLEAN datatype to end users

Hi Kathey, Thanks for pointing me at this piece of the release machinery. I have a naive question: If we have this programmatic way of generating new release numbers and then poking them into test canons, what are we testing here? At first blush, it seems that we are just verifying that this

Re: Message round-trips between Derby client and server

Bryan Pendleton <[EMAIL PROTECTED]> writes: > Knut Anders Hatlen wrote: >> I haven't been thinking about the details, but at least it seems like >> this is what PostgreSQL and MySQL do. I think I may have jumped to the wrong conclusions here. I don't think PostgreSQL and MySQL are piggybacking Re

[jira] Assigned: (DERBY-807) Failure in derbyall/derbylang since r366564 | 2006-01-06 21:44:57 +0100 (Fri, 06 Jan 2006) | Add grantRevoke test to derbyLang suite.

[ http://issues.apache.org/jira/browse/DERBY-807?page=all ] Satheesh Bandaram reassigned DERBY-807: --- Assign To: Satheesh Bandaram Suspect the problem is because of forgetting to add new GrantRevoke nodes to JAR build process. Submitted a fix today

Re: Question about closing connection and statement objects

Deepa Remesh wrote: > Should a JDBC driver close the statement objects associated with a > connection when the connection's close() method is called? > > I saw this in JDBC 3.0 spec (Section 13.1.3 Closing Statement Objects) > "All Statement objects will be closed when the connection that created

Re: Question about closing connection and statement objects

Connection.close() is supposed to close open Statement objects. Deepa Remesh wrote: Should a JDBC driver close the statement objects associated with a connection when the connection's close() method is called? I saw this in JDBC 3.0 spec (Section 13.1.3 Closing Statement Objects) "All Statemen

Question about closing connection and statement objects

Should a JDBC driver close the statement objects associated with a connection when the connection's close() method is called? I saw this in JDBC 3.0 spec (Section 13.1.3 Closing Statement Objects) "All Statement objects will be closed when the connection that created them is closed." But I found d

Re: [Db-derby Wiki] Update of "DerbyDevActivities" by SatheeshBandaram

I already did that... You are seeing my intermediate results... I kept saving in the middle, old habit. Here is my first version of active developments as I have noticed. I know there are some more that I have missed. Before I continue further, any comments on the format? http://wiki.apache.o

Re: derby bay area lunch

I'd love to, but cannot make it up to the city for lunch very easily. Will be there in spirit =) -Brian

Re: derby bay area lunch

Count me in for the lunch (Feb 1st Wednesday). Regards, Rajesh

Re: [Db-derby Wiki] Update of "DerbyDevActivities" by SatheeshBandaram

If you want the Jira links to be actual links, here is what I do. [http://issues.apache.org/jira/browse/DERBY-573 DERBY-573] Apache Wiki wrote: > Dear Wiki user, > > You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for > change notification. > > The following page has

Re: derby bay area lunch

On Jan 6, 2006, at 4:45 PM, Rick Hillegas wrote: I'd like to setup a lunch for those of us in the Bay Area who are working on Derby. I'm thinking of Wednesday February 1 in San Francisco. Any interest? Unfortunately, I believe I'll be out of town. Somehow that always manages to happen wi

Re: [VOTE] Rick Hillegas as a committer

+1 David W. Van Couvering wrote: This vote is for establishing Rick Hillegas as a committer for Derby. Please vote +1 if you approve of Rick as a committer.

Re: [VOTE] Rick Hillegas as a committer

+1

Re: [jira] Commented: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.

I agree, at this point I think what you have implemented is a useful feature. It is much more online than 10.1 version. I agree with Oystein there may be ways to improve - but maybe those can be logged as new improvements. Suresh Thalamati wrote: Øystein Grøvlen wrote: Suresh, Thanks for co

Re: [VOTE] Rick Hillegas as a committer

+1, based on Rick's technical work and knowledge. He also brings right kind of humor and flair to the group! Satheesh David W. Van Couvering wrote: > This vote is for establishing Rick Hillegas as a committer for Derby. > Please vote +1 if you approve of Rick as a committer. > > I am nominating

[jira] Commented: (DERBY-499) Expose BOOLEAN datatype to end users

[ http://issues.apache.org/jira/browse/DERBY-499?page=comments#action_12362474 ] Daniel John Debrunner commented on DERBY-499: - The functional spec lists BOOLEAN to and from CLOB as being a valid cast. This does not match the existing behaviour

Re: Message round-trips between Derby client and server

Knut Anders Hatlen wrote: I haven't been thinking about the details, but at least it seems like this is what PostgreSQL and MySQL do. This blocking behaviour is an issue only in read committed mode, right? I found your comment very interesting because it made me realize that I hadn't been thin

Re: derby bay area lunch

Hi,   Wednesday Feb 1 would work fine for me...   Myrna 

Re: derby bay area lunch

Maybe we should send email to derby-user as well? The more inclusive we are, the more likely some of those derby-users will become derby-devers. David Rick Hillegas wrote: Hi Kathy, Absolutely! I'm sorry if I gave the impression that the lunch was limited to developers. -Rick Kathy Saund

Re: derby bay area lunch

Hi Kathy, Absolutely! I'm sorry if I gave the impression that the lunch was limited to developers. -Rick Kathy Saunders wrote: I'd be interested in coming if it's open to non-developers :-) Rick Hillegas wrote: So far, Jeff, David, and Kathey have rsvd. Anyone else interested? Would peo

Re: Grant and Revoke, Part I ... DERBY-464...

Satheesh Bandaram wrote: > Daniel John Debrunner wrote: > > >>I wonder if we should look at grant/revoke augmenting the existing >>authorization model instead of replacing it. > Why would we want to augment the new authorization model with the old > one? Is there something that old model provid

Re: [jira] Commented: (DERBY-499) Expose BOOLEAN datatype to end users

Rick Hillegas wrote: > Hi Kathey, > > I have clipped to JIRA-499 a fix for these regressions. Thanks for the > heads-up about the version numbers in the canons. I finessed that > issue by removing the volatile numbers from the canons. Instead, the > metadata test now compares version numbers inter

Re: Message round-trips between Derby client and server

Daniel John Debrunner <[EMAIL PROTECTED]> writes: > Dag H. Wanvik wrote: > >> Hi, >> >> >>>"Knut" == Knut Anders Hatlen <[EMAIL PROTECTED]> wrote: [...] >> Knut> My initial thought is that we should try to: >> Knut> >> Knut> 1) Pre-fetch rows in PreparedStatement.executeQuery(), saving on

Re: Grant and Revoke, Part I ... DERBY-464...

Francois Orsini wrote: > Comments inlined: > > On 1/10/06, *Daniel John Debrunner* <[EMAIL PROTECTED] > > wrote: > > > I wonder if we should look at grant/revoke augmenting the existing > authorization model instead of replacing it. > > > Well, it is not compl

Re: [VOTE] Rick Hillegas as a committer

David W. Van Couvering wrote: This vote is for establishing Rick Hillegas as a committer for Derby. Please vote +1 if you approve of Rick as a committer. [snip] +1 -- Ole

Re: [VOTE] Rick Hillegas as a committer

David W. Van Couvering wrote: > This vote is for establishing Rick Hillegas as a committer for Derby. > Please vote +1 if you approve of Rick as a committer. +1 Dag

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

[ http://issues.apache.org/jira/browse/DERBY-326?page=comments#action_12362446 ] Tomohito Nakayama commented on DERBY-326: - I upload DERBY-326_5.patch. - Description of patch : * Remove processing to expand data from InputStream of b

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

[ http://issues.apache.org/jira/browse/DERBY-326?page=all ] Tomohito Nakayama updated DERBY-326: Comment: was deleted > Improve streaming of large objects for network server and client > ---

[jira] Resolved: (DERBY-792) Intermittent java.security.PrivilegedActionException was happend in derbynet/runtimeinfo.java of derbynetclient

[ http://issues.apache.org/jira/browse/DERBY-792?page=all ] Tomohito Nakayama resolved DERBY-792: - Resolution: Invalid Because this issue was phenomena caused by uncommited patch of DERBY-326, this issue is invalid. > Intermittent java.securit

[jira] Commented: (DERBY-792) Intermittent java.security.PrivilegedActionException was happend in derbynet/runtimeinfo.java of derbynetclient

[ http://issues.apache.org/jira/browse/DERBY-792?page=comments#action_12362442 ] Tomohito Nakayama commented on DERBY-792: - I examined DERBY-326_5.patch. http://issues.apache.org/jira/browse/DERBY-326?page=all In this patch, finalizer method of ReEnc

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

[ http://issues.apache.org/jira/browse/DERBY-326?page=all ] Tomohito Nakayama updated DERBY-326: Attachment: DERBY-326_5.patch I upload DERBY-326_5.patch. - Description of patch : * Remove processing to expand data from InputStrea

[jira] Closed: (DERBY-746) NullPointerException when 'encryptionKey' length is an odd number, or it contains invalid chars

[ http://issues.apache.org/jira/browse/DERBY-746?page=all ] Kristian Waagan closed DERBY-746: - Fix Version: 10.2.0.0 Resolution: Fixed Spelling error fixed in revision 367712, thanks to Daniel John Debrunner. Verified changes by inspection, cl

Re: [VOTE] Rick Hillegas as a committer

David W. Van Couvering wrote: This vote is for establishing Rick Hillegas as a committer for Derby. Please vote +1 if you approve of Rick as a committer. [snip] +1 -- Kristian

Re: [jira] Updated: (DERBY-212) Optimize some specific methods in Network Server to improve performance

Bernt M. Johnsen wrote (2006-01-11 12:52:27): > > Then we'll just have to wait for a committer's attention. Any > > volunteers? :) > > I volunteer Next time you submit a patch: please attach the output from svn stat as a separate file. Then I can use diff instead of manual inspec

Re: [jira] Updated: (DERBY-212) Optimize some specific methods in Network Server to improve performance

Knut Anders Hatlen wrote (2006-01-11 08:41:06): > Bryan Pendleton <[EMAIL PROTECTED]> writes: > > > Knut Anders Hatlen (JIRA) wrote: > >> I have uploaded a new patch (DERBY-212-parsePKGNAMCSN-2.diff) where I > >> have tried to address Bryan's review comments. > > > > Hi Knut Anders, >

Re: Message round-trips between Derby client and server

"Dag H. Wanvik" <[EMAIL PROTECTED]> writes: > Hi, > >> "Knut" == Knut Anders Hatlen <[EMAIL PROTECTED]> wrote: > > Knut> > Knut> | Derby | DB2 univ | Postgres | MySQL > Knut> - > Knut> DriverMa

Re: Grant and Revoke, Part I ... DERBY-464...

Daniel John Debrunner wrote: >I wonder if we should look at grant/revoke augmenting the existing >authorization model instead of replacing it. > > > Why would we want to augment the new authorization model with the old one? Is there something that old model provides that new model doesn't have?

Re: running JUnit tests

John Embretsen wrote: Andreas Korneliussen wrote: I propose to introduce a new test type called "junit" (current test types are: sql,sql2,unit,java,multi,demo - unit is not junit) Then you can use: java org.apache.derbyTesting.functionTests.harness.RunTest .junit to run a Junit test - ins

Re: [VOTE] Rick Hillegas as a committer

David W. Van Couvering wrote: This vote is for establishing Rick Hillegas as a committer for Derby. Please vote +1 if you approve of Rick as a committer. +1

Re: [VOTE] Rick Hillegas as a committer

+1 Andreas

Re: [VOTE] Rick Hillegas as a committer

> "DWVC" == David W Van Couvering <[EMAIL PROTECTED]> writes: DWVC> This vote is for establishing Rick Hillegas as a committer for DWVC> Derby. Please vote +1 if you approve of Rick as a committer. +1 -- Øystein

Re: Grant and Revoke, Part I ... DERBY-464...

Comments inlined:On 1/10/06, Daniel John Debrunner <[EMAIL PROTECTED]> wrote: I wonder if we should look at grant/revoke augmenting the existingauthorization model instead of replacing it. Well, it is not completely replaced since legacy would still be supported (until sqlStandard is set explicitly