On Mon, Mar 22, 2004 at 06:15:48PM -, Martin J. Evans wrote:
> I have only just seen this and am thinking about it. In the mean time:
>
> > Taking it a little further, following the lead of DBD::ODBC, it would be
> > convienient to be able to automatically skip pass non-SELECT statements
> > i
I have only just seen this and am thinking about it. In the mean time:
> Taking it a little further, following the lead of DBD::ODBC, it would be
> convienient to be able to automatically skip pass non-SELECT statements
> if an attribute is set. Something like:
The code in DBD::ODBC 1.09 appears
Subject changed from "test_dynamic Error 29 installing DBD-Oracle v 1.15
on red hat 9 Oracle 9.2"
To be honest, it is stunning how complicated they (oracle/we in IT?)
have made this. Its indicative of a moving spec, and lack of
agreement. Which is obvious when one reads the oracle documentation.
Could you guys look at 21nchars.t or sub print_nls_info in
30long.t.
I do not think it is a good idea to select from V$ tables: many users
are not granted permission to see select from those. I have not checked
8i, but in 9i a safe way to to this is to select from
NLS_DATABASE_PARAMETERS, as in
On Sun, Mar 21, 2004 at 01:10:27PM -0800, Dean Arnold wrote:
> 2. The charset used for client<->server transfer syntax
> may not be the same as the internal storage charset
> of the DBMS (e.g., UTF8 may be used for transfer,
> but the target columns may be Latin1; attemping
> to insert a non-Latin1
