I have an outstanding enhancement request for support of the SQL standard to add DEFAULT values of CURRENT_DATE equal to #DATE CURRENT_TIME equal to #TIME CURRENT_TIMESTAMP equal to #NOW.
Using a computed column doesn't work for me as a reload resets the value whereas I am using such a field to track changes for audit purposes. Perhaps in v9.0. Jim Bentley American Celiac Society [email protected] tel: 1-504-737-3293 --- On Wed, 1/28/09, [email protected] <[email protected]> wrote: > From: [email protected] <[email protected]> > Subject: [RBASE-L] - Re: ERROR- Specified default value is not valid for > column Relea... > To: "RBASE-L Mailing List" <[email protected]> > Date: Wednesday, January 28, 2009, 10:09 AM > Yeah, this is real familiar to me! Way back in Nov 2007 I > reported this as > a "bug". I did an unload and a load to fix a > corrupted database and it hung > on a default .#DATE column with the exact message you got. > RBTI did not > change this behavior: "Solution Provided (not a > bug)". I can't remember what > they told me to do -- I think I had to change it to a > computed column rather than > a default?? > > Karen > > > > I'm reloading a table and I guess this is a > tightening up that I have > > missed. > > > > The column is (not surprisingly) a DATE column and > the default is : > > (.#DATE) > > > > I've tried un-dotted and without brackets but > still get the error. > > > > Stranger, I have two other similar columns, > Entry_Date &Up_Date, one of > > which has the same default but the other is computed > rather than defaulted and > > uses an Expression with the calculation: (.#DATE). > Both these columns follow > > the ReleaseDate in the table so I don't know (yet) > if either will fail also. > > > > Any thoughts, anybody? > > > > Regards, > > > > Alastair > > > > > >
