T.R | Title | User | Personal Name | Date | Lines |
---|
1084.1 | However you need a formal response | NOVA::SMITHI | Don't understate or underestimate Rdb! | Tue Apr 29 1997 16:52 | 9 |
| ~I wouldn't think it would be effected, due to the fact that time-stamped data
~isn't stored in the CDD,
Actually timestamped data *is* stored in the CDD. But as it is base don Rdb
then it also uses the same time information.
I wouldn't expect CDD to be affected by this bug or the Year 2000.
Ian
|
1084.2 | FWIW | 8292::PJACOB | Patrick [email protected] | Wed Apr 30 1997 12:08 | 21 |
| >I wouldn't expect CDD to be affected by this bug or the Year 2000.
I won't call it a bug since it is a documented restriction prior to VMS
7.1 for:
LIB$CVT_TO_INTERNAL_TIME
LIB$CVT_FROM_INTERNAL_TIME
LIB$CVTF_TO_INTERNAL_TIME
LIB$CVTF_FROM_INTERNAL_TIME
LIB$CVT_VECTIM
LIB$ADD_TIMES
LIB$SUB_TIMES
LIB$MULT_DELTA_TIME
LIB$MULTF_DELTA_TIME
LIB$CONVERT_DATE_STRING.
When I asked this question to CDD/Administrator ( NOMAHS::CDDT 354 ), the
answer was that CDD/Administrator would not be impacted by this
restriction. I assumed that CDD/Repository would not be impacted too
but a formal answer from CDD/Repository too would be better.
Patrick
|
1084.3 | | CDDA::MITCHNECK | Colleen Mitchneck; Oracle NEDC | Mon May 19 1997 09:18 | 3 |
| The only one of these routines that CDD uses is LIB$CONVERT_DATE_STRING. It is
only used to process "TODAY", "TOMORROW" & "YESTERDAY". We don't anticipate any
problems with these.
|