Thanks Ann,

Any idea if there are plans by anyone to ressurect the write ahead log?
It would be usefull in alot of situations (it would be excellent in a few of
our environments)
David has sworn by the practise since his last foray with Oracle.

best regards

Dalton

On Monday 10 September 2001 12:26, you wrote:
> At 11:17 AM 9/10/2001 -0400, Dalton Calford wrote:
> >BASED
>
> a GDML keyword recognized by GPRE and QLI. GDML keywords can
> overlap object names
>
> >BASENAME
> >BASE_NAME
>
> An SQL keyword use for controlling the log files of the obsolete
> Write After Log (WAL)
>
> >DISPLAY
>
> A seriously obsolete GPRE keyword used by PYXIS forms package
>
> >OCTET_LENGTH
>
> Apparently unused, but obviously related to OCTETS.
>
> >RAW_PARTITIONS
>
> Another SQL keyword for controlling WAL files
>
> >VERSION
>
> SQL keyword establishing the type of transaction. VERSION and
> NO VERSION are used with READ_COMMITTED transactions to determine
> whether they work or not.
>
> >WRITE
>
> SQL keyword used in establishing either access type (READ WRITE)
> or the desired table lock level (WRITE)
>
>
>
> Regards,
>
> Ann
> www.ibphoenix.com
> We have answers.
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/