Buddy you can only set it as a "computed column". This would have the problem of recomputing on reloads. Other SQL implementations and SQL standards provide the following definitions which could provide the functionality but have not been implemented by RBTI. CURRENT_DATE which is equivalent to .#DATE CURRENT_TIME which is equivalent to .#TIME CURRENT_TIMESTAMP which is equivalent to .#NOW
I have had an enhancement request to provide this functionality but as of yet they have not been implemented. Perhaps if enough users request it some future update will include this functionality. Until then only a constant value for example '05/20/2012' can be defined or you could use a computed column with its reload problems. Another way to take care of this would be in a BEFORE INSERT and a BEFORE UPDATE trigger but as presently implemented "WHERE CURRENT OF SYS_NEW" in those two events are defined as read only cursors and cause recursive execution of the trigger. Many competitive products make the SYS_NEW data update-able without triggering recursion. Jim Bentley American Celiac Society [email protected] tel: 1-504-737-3293 >________________________________ > From: "Walker, Buddy" <[email protected]> >To: RBASE-L Mailing List <[email protected]> >Sent: Thursday, May 24, 2012 11:08 AM >Subject: [RBASE-L] - RE: DEFAULT > >Albert > > Yes, but you could have problems with that. For instance you reload >the database that column will now reflect the current date. > >Buddy > > >-----Original Message----- >From: [email protected] [mailto:[email protected]] On Behalf Of Albert >Berry >Sent: Thursday, May 24, 2012 11:59 AM >To: RBASE-L Mailing List >Subject: [RBASE-L] - DEFAULT > >I'm having a brain fart. Can I set a column default to .#DATE? >Albert > > > > >
