RE: Default user ID in SQL table

Duane,

These are validation tables so I guess I will have to either use SQL to populate them or manually update the user ID's for now. Not a big deal in this case, I just wanted to get a better understanding of what was going on.

I don't know how I missed the default values documentation. If I had a paper copy of the SQL Reference manual it would be worn out by now. We are at 5.4 but it isn't shown there either. Thanks for pointing that out.

Rick

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Christen, Duane
Sent: Monday, May 18, 2009 8:53 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Default user ID in SQL table

Rick;

As Vern said, DBU is passing blanks as the value of the field, not null thus the DDL default clause is not invoked, an RPG write would have the same problem. If you wrote to a LF or index that did not contain the field in the record format the default value would be used.

In a quick test DBU populated the default value into a defaulted field on the add display.

For an RPG write another possibility would be to allow the defaulted field to contain null and set the null indicator before the write. I would expect this to work but I have not tested it.

As to the SYSTEM_USER SESSION_USER issue, the 6.1 sql reference does not allow them in the default clause:
default-clause

.-WITH-.
|--+------+--DEFAULT--+-------------------------------------------------+--|
+-constant----------------------------------------+
+-USER--------------------------------------------+
+-NULL--------------------------------------------+
+-CURRENT_DATE------------------------------------+
+-CURRENT_TIME------------------------------------+
+-CURRENT_TIMESTAMP-------------------------------+
'-cast-function-name--(--+-constant----------+--)-'
+-USER--------------+
+-CURRENT_DATE------+
+-CURRENT_TIME------+
'-CURRENT_TIMESTAMP-'


Duane Christen


--


Duane Christen
Senior Software Engineer
(319) 790-7162
Duane.Christen@xxxxxxxxxx

Visit PAETEC.COM


Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.