[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lmi-commits] [lmi] master 284339d 1/8: Document boolean database entiti
From: |
Greg Chicares |
Subject: |
[lmi-commits] [lmi] master 284339d 1/8: Document boolean database entities more uniformly |
Date: |
Wed, 7 Nov 2018 17:11:09 -0500 (EST) |
branch: master
commit 284339d92d2828b96e55f54ba1c68aa5c89475e7
Author: Gregory W. Chicares <address@hidden>
Commit: Gregory W. Chicares <address@hidden>
Document boolean database entities more uniformly
---
dbnames.xpp | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/dbnames.xpp b/dbnames.xpp
index 8e6ef65..4e93885 100644
--- a/dbnames.xpp
+++ b/dbnames.xpp
@@ -126,10 +126,10 @@
{DB_GenAcctIntBonus,DB_Topic_Interest,"GenAcctIntBonus","Interest bonus added
to the general account rate",}, \
{DB_BonusInt,DB_Topic_Interest,"BonusInt","Bonus interest [not yet
implemented]",}, \
{DB_IntFloor,DB_Topic_Interest,"IntFloor","[not used]",}, \
-{DB_AllowGenAcct,DB_Topic_Interest,"AllowGenAcct","Allow investment in general
account",}, \
-{DB_AllowSepAcct,DB_Topic_Interest,"AllowSepAcct","Allow investment in
separate account",}, \
-{DB_AllowGenAcctEarnRate,DB_Topic_Interest,"AllowGenAcctEarnRate","Allow entry
of general-account earned rate",}, \
-{DB_AllowSepAcctNetRate,DB_Topic_Interest,"AllowSepAcctNetRate","Allow entry
of separate-account net rate",}, \
+{DB_AllowGenAcct,DB_Topic_Interest,"AllowGenAcct","Allow investment in general
account: 0=no, 1=yes",}, \
+{DB_AllowSepAcct,DB_Topic_Interest,"AllowSepAcct","Allow investment in
separate account: 0=no, 1=yes",}, \
+{DB_AllowGenAcctEarnRate,DB_Topic_Interest,"AllowGenAcctEarnRate","Allow entry
of general-account earned rate: 0=no, 1=yes",}, \
+{DB_AllowSepAcctNetRate,DB_Topic_Interest,"AllowSepAcctNetRate","Allow entry
of separate-account net rate: 0=no, 1=yes",}, \
{DB_MaxGenAcctRate,DB_Topic_Interest,"MaxGenAcctRate","Maximum general account
interest rate",}, \
{DB_MaxSepAcctRate,DB_Topic_Interest,"MaxSepAcctRate","Maximum separate
account interest rate",}, \
{DB_SepAcctSpreadMethod,DB_Topic_Interest,"SepAcctSpreadMethod","Separate-account
spread and fee subtraction: 0=annual (effective), 1=daily (nominal)",}, \
@@ -206,13 +206,13 @@
{DB_MinRenlBaseSpecAmt,DB_Topic_DeathBenefits,"MinRenlBaseSpecAmt","Minimum
specified amount after issue for base policy only, ignoring any term rider",}, \
{DB_MaxIssSpecAmt,DB_Topic_DeathBenefits,"MaxIssSpecAmt","Maximum specified
amount allowed at issue [not yet implemented]",}, \
{DB_MaxRenlSpecAmt,DB_Topic_DeathBenefits,"MaxRenlSpecAmt","Maximum specified
amount after issue [not yet implemented]",}, \
-{DB_AllowDbo1,DB_Topic_DeathBenefits,"AllowDbo1","Allow level death benefit
option",}, \
-{DB_AllowDbo2,DB_Topic_DeathBenefits,"AllowDbo2","Allow increasing death
benefit option",}, \
-{DB_AllowDbo3,DB_Topic_DeathBenefits,"AllowDbo3","Allow return of premium
death benefit option",}, \
+{DB_AllowDbo1,DB_Topic_DeathBenefits,"AllowDbo1","Allow level death benefit
option: 0=no, 1=yes",}, \
+{DB_AllowDbo2,DB_Topic_DeathBenefits,"AllowDbo2","Allow increasing death
benefit option: 0=no, 1=yes",}, \
+{DB_AllowDbo3,DB_Topic_DeathBenefits,"AllowDbo3","Allow return of premium
death benefit option: 0=no, 1=yes",}, \
{DB_AllowChangeToDbo2,DB_Topic_DeathBenefits,"AllowChangeToDbo2","Allow change
to increasing death benefit option: 0=no, 1=yes",}, \
{DB_DboChgCanIncrSpecAmt,DB_Topic_DeathBenefits,"DboChgCanIncrSpecAmt","Option
changes can increase specified amount to preserve net amount at risk",}, \
{DB_DboChgCanDecrSpecAmt,DB_Topic_DeathBenefits,"DboChgCanDecrSpecAmt","Option
changes can decrease specified amount to preserve net amount at risk",}, \
-{DB_AllowExtEndt,DB_Topic_DeathBenefits,"AllowExtEndt","Allow coverage beyond
normal maturity ('extended endowment') [not yet implemented]",}, \
+{DB_AllowExtEndt,DB_Topic_DeathBenefits,"AllowExtEndt","Allow coverage beyond
normal maturity ('extended endowment'): 0=no, 1=yes [not yet implemented]",}, \
{DB_Topic_Riders,DB_FIRST,"Riders","Riders and other additional benefits",}, \
{DB_AllowTerm,DB_Topic_Riders,"AllowTerm","Allow term: 0=no, 1=yes",}, \
{DB_GuarTermTable,DB_Topic_Riders,"GuarTermTable","Term guaranteed mortality
charge table (index in mortality table database)",}, \
- [lmi-commits] [lmi] master updated (259f97c -> 6c72fcf), Greg Chicares, 2018/11/07
- [lmi-commits] [lmi] master 284339d 1/8: Document boolean database entities more uniformly,
Greg Chicares <=
- [lmi-commits] [lmi] master e4a6ba2 6/8: Use query<bool> with database entities that are inherently boolean, Greg Chicares, 2018/11/07
- [lmi-commits] [lmi] master 39f76e4 4/8: Make a deliberate mistake more obvious in a unit test, Greg Chicares, 2018/11/07
- [lmi-commits] [lmi] master f066478 7/8: Use query<T> with database entities that are inherently enumerative, Greg Chicares, 2018/11/07
- [lmi-commits] [lmi] master 6c72fcf 8/8: Use query<double> with database entities that are inherently floating, Greg Chicares, 2018/11/07
- [lmi-commits] [lmi] master 5e009d6 3/8: Adjust whitespace to improve vertical alignment, Greg Chicares, 2018/11/07
- [lmi-commits] [lmi] master 28105c5 5/8: Use query<int> with database entities that are inherently int, Greg Chicares, 2018/11/07
- [lmi-commits] [lmi] master 9490b4c 2/8: Avoid using floating-point constants for boolean values, Greg Chicares, 2018/11/07