Re: Sun, Java and BigDecimal incompatible changes in J2SE 5.0

I am trying ot track this down from my end as well. hopefully we will find out what's up on this lance Daniel John Debrunner wrote: David Van Couvering wrote: Hi, Dan, still tracking this down, but I had to smile -- the first level answer I got back from the J2SE folks was that

Re: [VOTE] accept derby client contribution

[+ ] +1: Accept the contribution of the derby client Satheesh Bandaram wrote: I just realized I called for a vote to accept Derby client without the [VOTE] subject header, in the middle of a longish email. I would like to reissue the call for vote. I call for all those who voted already to vote

Re: Proposed changes to the NetworkServer stop and start scripts

Thanks Andrew. -Lance Andrew McIntyre wrote: On Apr 12, 2005 5:41 AM, Lance Andersen [EMAIL PROTECTED] wrote: Attached are the diffs for the NetworkServer start and stop scripts. The changes allow the user to specify the host/port on the command line or via the variables

Re: [jira] Created: (DERBY-199) Derby does not support array of column names or column indexes to execute or executeUpdate. Document incorrectly implies that Derby supports this functionality

Yes i will be happy to lance David Van Couvering wrote: Would you be willing to log a JIRA feature request for this... David Lance J. Andersen wrote: FWIW, we should support column names for autoGeneratedKeys. Most vendors now support this feature so adding it will ease migration issues

Re: Questions about getApproximateLengthInBytes()

I raised this as a clarification issue with the EG so that we can have a discussion on this. My hope is to close on this within the next week. I am trying to clean-up issues like this for JDBC 4. However, some issues might not get addressed until after the first EDR. I hope to address as

Re: [jira] Commented: (DERBY-194) getPrecision() on TIME and TIMESTAMP is zero

We have been having a similar discussion in the JDBC 4.0 EG group regarding the DatabaseMetaData.getTypeInfo PRECISION column. The intent of the JDBC spec was to match the behavior specified for ODBC. I will bring this up as a point to clarify for JDBC 4.0 in the EG.. Regards Lance Daniel

Re: [jira] Commented: (DERBY-194) getPrecision() on TIME and TIMESTAMP is zero

BTW, here is the docs for ODBC for the PRECISION column which as of ODB 3.0 is now known as COLUMN_SIZE The maximum column size that the server supports for this data type. For numeric data, this is the maximum precision. For string data, this is the length in characters. For datetime data

Status of the New Client network JDBC driver

I was wondering if there is any update to when the New Client JDBC driver will be added to the derby workspace? Last I had heard it was to be march. Regards Lance

Re: [VOTE] Reject tally of logo votes

+1 Kathey Marsden wrote: It seems to me that it would be very sad and bad karma to have our logo under such a cloud of suspicion. So I would like to call a vote to reject this tally. I've heard lots of great ideas on how to resolve this issue either technologically or socially but I

Re: On DERBY-107 : ODBC Metadata functions

3) Extra columns in ODBC. For getProcedureColumns, the spec explicitly says it's ok to have extra columns. I wonder if that would be ok for other methods too. It turns out that, aside from getProcedureColumns, the only other metadata function for which ODBC specifies columns that JDBC

Re: [PATCH] Change all Identifier Limitations to 128

+1 IMHO. Regards Lance Philipp Hug wrote: Ok, I could create a new patch that also renames DB2_ into DERBY_ and renames DB2Limit into DerbyLimit. How does that sound? philipp Lance J. Andersen wrote: If the changes being made differ from the DB2 limits, and it does make sense to change

Re: [PATCH] Change all Identifier Limitations to 128

If the changes being made differ from the DB2 limits, and it does make sense to change this now that Derby is part of apache, I would pull the constants out of DB2Limit.java as this seems confusing from the outside looking in.

Re: [PATCH] Change all Identifier Limitations to 128

If the changes being made differ from the DB2 limits, and it does make sense to change this now that Derby is part of apache, I would pull the constants out of DB2Limit.java as this seems confusing from the outside looking in. Philipp Hug wrote: this patch changes maximum length of column

Re: Thoughts on the Derby Developer Community

I had another possible thought. Could we consider doing a bi-weekly call where we discuss some component of the Derby architecture? This might be a way to get folks up to speed a bit quicker as well. Daniel John Debrunner wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan

Re: Thoughts on the Derby Developer Community

I think I am going to take this suggestion back. A friend of mine who has worked on open source projects for a long time reminded me that this is not the norm for open source projects for a variety of very valid reasons. enjoy the weekend! Lance J. Andersen wrote: I had another

<    1   2   3