Re: WebDB Howto use Sequences when inserting new records

Wow...that WORKS! Kind of... here's what I have to do to make it work:

After setting the Default Value in my forms to#LOWER(USER), when I add the new component to the WebDB site, I CANNOT add it as a WebDB component, but rather I add it as a URL, directly calling the stored procedure. For some reason, adding it as a Webdb component makes it so the user is ALWAYS <schema>_public, doing it the other way, it calls it as the ACTUAL user...a REAL gotcha, I'd say!!!

Thanks for your tip!

"M. Oberly" wrote:

> Hello,
>
> To get current logged-in Oracle userid into a Form field, specify the field's
>
> Default Value as "#USER". This gets you the userid in uppercase. Using
> "#LOWER(USER)" gets the userid in lowercase. In this context, the "#"
> character serves as an escape character allowing SQL functions to be
> placed into WebDB Forms.
>
> Regards,
> Mark
> mao_at_dde.dk
>
> Win Ker wrote:
>
> > EASIEST way is to design your schema using Oracle Designer, generate your
> > tables & related sequences, then generate the table API which will build
> > the related triggers, etc. Upon which, in WebDB, create your form, and on
> > the PK column, set it to Not Mandatory and it will automagically be
> > populated by the sequence...worked great for me.
> >
> > A few things that DON'T work for me is that I cannot do a "select user
> > from dual" to populate a table with the form username...always returns
> > <dad>_public as the value...anyone have any idea of how to retrieve the
> > username for a particular session of WebDB???
> >
> > "Paul O. Schenker" wrote:
> >
> > > Hi,
> > >
> > > what must I do when configuring Input Forms to make use of an existing
> > > sequence for the primary key?
> > >
> > > Thanks for a hint.
> > >
> > > Paul
Received on Wed Sep 29 1999 - 15:54:04 CEST