Sean Kelly <[EMAIL PROTECTED]> writes:
> Does DBD::Oracle support bulk binds at the Oracle OCI level? I know from
> the DBI documentation that you can submit an array of parameters
> to "execute" but the docs state that the default behaviour is for DBI to
> iterate over each set of values an
"Anniballi, Fran" <[EMAIL PROTECTED]> writes:
> For option two, if I have two versions of DBD:Oracle, how do I tell
> Perl which one to use? My scripts just say "/usr/bin/perl" in the
> first line.
Basically, when you compile you use the PREFIX option:
export ORACLE_HOME=/usr/local/oracle8
"Anniballi, Fran" <[EMAIL PROTECTED]> writes:
> As soon as I recompile the same DBI/DBD with it pointing to Oracle 9
> environment (libraries), it doesn't work. It is looking for Oracle9
> library files and I obviously don't have it pointing to oracle9
> libraries when I access an Oracle 8 instan
to switch back to the old 5.6 (unsafe)
signal handling mode for immediate signal handling (not sure of the
details).
What would be interesting is if DBD::Oracle could be extended to handle
signals explicitly to enable safe aborting of DBI operations. Not sure
what that would involve, though.
- Kr
"Rozengurtel, Daniel" <[EMAIL PROTECTED]> writes:
> With no RowCacheSize set up the extract took 34 secs, using about
> 5mb RAM
> With RowCacheSize =>0 (automatically select what's best), the
> extract took 33 secs, with 5mb RAM
> With RowCacheSize =>100, the extract took 8 secs
trips and
latency is a bottleneck for you. You could try different values and see
if it makes any difference.
- Kristian.
--
Kristian Nielsen [EMAIL PROTECTED]
Development Manager, Sifira A/S
"Inbal Mozes (DBA)" <[EMAIL PROTECTED]> writes:
> I am trying to find a solution for multiplies oracle home on Unix machines .
> Currently , for each new oracle home on the machine , a new compilation of perl with
> DBD/DBI is necessary .
Well, it is not necessary to recompile Perl or DBI, a se
"Peter J. Holzer" <[EMAIL PROTECTED]> writes:
> few times, so I think others are interested, too. Can you post the patch
> or a pointer to the dbi-dev archive?
http://aspn.activestate.com/ASPN/Mail/Message/perl-DBI-dev/1686549
(note, the patch is against DBD::Oracle 1.14).
- Kristian.
"M. Addlework" <[EMAIL PROTECTED]> writes:
> > > Kristian Nielsen [EMAIL PROTECTED] wrote:
> > >> Could you briefly explain what an INSERT/UPDATE cursor is?
> UPDATE set = where CURRENT OF X;
> The original poster was correct that you can'
t I posted a patch to [EMAIL PROTECTED] a few
months back. There was no interest at the time, though I do expect to
clean it up and get it into the official DBD::Oracle eventually.
- Kristian.
--
Kristian Nielsen [EMAIL PROTECTED]
Development Manager, Sifira A/S
"Zachary Buckholz" <[EMAIL PROTECTED]> writes:
> But since my perl code runs from the crontab sometimes jobs overlap
> and I might be popping mail for more then one site's feedback address
> at a time and thus making multiple inserts into the MS SQL database
> server. Then I get these damn deadloc
Jared Still <[EMAIL PROTECTED]> writes:
> If you are working with Oracle, or any database for that matter,
> one of the cardinal performance rules for programming is to do
> it in SQL in possible. It is much faster than anything you
> can write in Perl, or any other language for that matter.
>
>
r databases I would assume), tablespaces, tables, columns,
and so on are not literals, they are identifiers and so cannot use
placeholders.
I believe the DBI explanation cited above is more technically accurate,
though.
- Kristian.
--
Kristian Nielsen [EMAIL PROTECTED]
Development Manager, Sifira A/S
To follow up on Tom's good examples, which I believe were run on Perl 6,
I decided to try with Perl 5.8.0, and I found that version of Perl _is_
indeed a lot better.
In Perl 5.8, the idea is that the internal representation (single-byte
or utf8) should not be visible to the programmer. So Perl may
er
single-byte or utf8 internal encoding, but in practise I think the best
is to use single-byte internal representation when all characters are <=
127, and utf8 internal representation otherwise.
I hope this explanation helps somewhat, the issue is admittedly
complex (and the above only IMHO, of course).
- Kristian.
--
Kristian Nielsen [EMAIL PROTECTED]
Development Manager, Sifira A/S
both Solaris and Linux.
Not sure why other people have more trouble than that, but I must say I
do not know if our Solaris version is 32 or 64 bits, or indeed anything
about the 32/64 bit issue in our application. I can check if someone
asks me with directions about what to look for.
- Kristian.
"Perry and Lorae Merritt" <[EMAIL PROTECTED]> writes:
> I recently upgraded my linux server from redhat 7.0 to 8.0. In the process,
> the perl interface to my mysql database seems to have been broken. I have a
> [Wed Jan 29 18:13:02 2003] [error] [client 10.20.1.1] DBI object version
> 1.30 does
Tim Bunce <[EMAIL PROTECTED]> writes:
> On Wed, Jan 08, 2003 at 09:50:16AM -, Ben Middleton wrote:
> > It turns out that my problem was due to my database character set having
> > been UTF8 based. Resetting the NLS_LANG env to a non UTF8 character set
> > resolved this testing issue.
> > How
18 matches
Mail list logo