On Wed, Nov 18, 2015 at 1:40 AM, Rick Hillegas <rick.hille...@gmail.com> wrote: > Hi Trejkaz, > > What version of Derby did you use to create the original schema? This > behavior (COLUMN_DEF = NULL) goes back at least as far as Derby 10.10.1.1. > There is no semantic difference between a column which is declared without a > default and a column which is declared as DEFAULT NULL.
This is good news, so it's okay to remove that from our definitions without changing behaviour, and dropping the defaults will have no negative effect. I'm guessing the person who put them in was putting in integer columns and just wasn't sure whether the default was going to be null or 0, but I tested that myself already and found exactly what you posted in your reply, that it does default to null. The original schema long ago would have been created under 10.1.x.x or something similarly ancient. The furthest I can go back viewing the history is 10.4.x.x but it doesn't go back as far as the schema does. TX
