The org.apache.derby.client.am.ColumnMetaData has no DB2_SQLTYPE_NUMERIC case for getColumnMetaDataType() function.
Similarly in org.apache.derby.client.am.Types I updated the case for NUmeric type and also in drda's SqlType.java.
The above changes gave the correct metadata.
But as this looks like a protocol change would like to know which test case will check derbyclient and drda layer.
And also is there any specific reason for using decimal for both numeric and decimal types.
DERBY-4901 might be an easy one too and if you like protocol, build up to DERBY-4805 .On 3/1/2011 10:47 AM, Rick Hillegas wrote:
On 3/1/11 7:33 AM, vipul modi wrote:
I am new to derby and would like to work on client server layer of derby db.
Can anyone suggest a initial starting point so that , it can get started with derby development.
MSc.(Tech) Information System
BITS-Pilani Goa Campus
One place to start would be to start fixing some of the discrepancies between the client and embedded drivers. Look for open JIRA issues which have the "Embedded/Client difference" box checked. DERBY-584 might be an easy one to start with
In general when working with Derby I think it is good to do the tutorial first.
Then get your build and test environment set up. See:
(also the relevant specifications are at the bottom of this page)
and if you want to use eclipse, Tiago made a nice screen cast for this at:
I would suggest you make sure suites.All and derbyall run before you start making code changes, so you can work out any kinks separate from your code changes.
Welcome and please do not hesitate to ask questions.