| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 <2015> 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 <2015> 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | recGblInitConstantLink broken in 3.16 |
| From: | Michael Davidsaver <[email protected]> |
| To: | "[email protected]" <[email protected]> |
| Date: | Mon, 16 Mar 2015 16:42:43 -0400 |
I broke it (to avoid the suspense). Only 3.16 branch is effected. It seems that my recent link field parsing changes have broken initialization of VAL in output records (really anything which call recGblInitConstantLink()). I missed a subtle distinction between constantStr==NULL and constantStr=="" during initialization. recGblInitConstantLink() treats NULL as a no-op, and "" as equivalent to "0". This comes about if a link field definition provides an initial() value. (see dbAllocRecord()). This breaks non-default values in .db files and autosave pass0. Test case and fix are forthcoming.