> I looked back through my emails from when I backed this change out and
> can't figure out which test I regressed. The reason that I backed the
> change out rather than fix the problem is because we were in the middle of
> trying to cut a release. I'll open a new JIRA soon here and just recommit
> the change to trunk for Derby / DB2 and fix the bug(s) when it rolls in.
Derby used in my unit test, I will test the trunk when you commit in.
Originally I use HSQLDB 2.2.8
for my test. But HSQLDB dictionary ignore (precision, scale), unit test failed
because my data round up to integer.
Than I changed to use Derby, It generate DOUBLE for BigDecimal so I researched
this problem.
This is the workaround I am using now.
// For hsqldb
public class TestHSQLDictionary extends HSQLDictionary {
public TestHSQLDictionary() {
fixedSizeTypeNameSet.remove("NUMERIC");
}
}
//For Derby
public class TestDerbyDictionary extends DerbyDictionary {
/**
*
*/
public TestDerbyDictionary() {
super();
numericTypeName = "NUMERIC";
fixedSizeTypeNameSet.remove("NUMERIC");
nextSequenceQuery="SELECT NEXT VALUE FOR {0} FROM
SYSIBM.SYSDUMMY1";
}
}
>> Is there any reason to ignore (precision, scale) of numeric on postgres?
> If I made the change for postgres, is this something you would be able to
> test?
I use postgres 9.1 in my project. I can test it with postgres 9.1.
