> You may be able to work around this by defining
> PERL_ENV_TABLES to LNM$FILE_DEV, and then defining
> LNM$FILE_DEV to the list of tables that you want.
>
Your suggestion does have merit, but the original reason that I
started looking into PERL_ENV_TABLES is because of a need to
ensure that perl doesn't use LNM$FILE_DEV...
Because Oracle 9.2 inserts its own table at the beginning
of LNM$FILE_DEV like this:
"LNM$FILE_DEV" = "SERVER_810111112"
= "LNM$PROCESS"
= "LNM$JOB"
= "LNM$GROUP"
= "LNM$SYSTEM"
= "DECW$LOGICAL_NAMES"
and when a perl script then sets an environment variable,
e.i. a logical name, then it ends up in the first table
on the list that you have write access to - which in
this case can be the oracle table - with possible bad
prospects like setting a NLS_LANG value that thereafter
affects the whole system adversely.
> On Thursday, October 21, 2004, at 07:55AM,
> <[EMAIL PROTECTED]> wrote:
>
Regards
Jakob Snoer
Nordic Processor
Data Warehouse Handel Drift / 8612
Tlf 436736
[EMAIL PROTECTED]
