On 6/12/06, Ron Savage <[EMAIL PROTECTED]> wrote:
Using a DSN of dbi:ODBC:xyz, the DBI -> connect(...) call takes 16 (sic)
seconds
with both the Perl script and Oracle running on the same PC under Windows.
You have been warned :-(.
I've occasionally seen similar outrageously long connection
Hi Folks
Using a DSN of dbi:ODBC:xyz, the DBI -> connect(...) call takes 16 (sic) seconds
with both the Perl script and Oracle running on the same PC under Windows.
You have been warned :-(.
--
Cheers
Ron Savage, [EMAIL PROTECTED] on 13/06/2006
http://savage.net.au/index.html
Let the record show:
On Mon, 12 Jun 2006 17:37:22 +0200, Alexander Foken wrote:
Hi Alexander
> Why don't you use DBD::Pg?
because, as OP was kind enough to explain...
>> (Speed-readers please note, this is Progress, not Postgres)!!
unless of course you have some reason for believing the PostgreSQL driver will
work
On Mon, 12 Jun 2006 15:24:55 +0100 (BST), Martin J. Evans wrote:
Hi Martin
>> This seems to fall into the category of the first quote from the
I saw the original post, and expected someone else to answer.
I don't agree that it falls in the first category. I strongly suspect you'll
have to amend
On Mon, 12 Jun 2006 14:50:55 -0700, Kevin Moore wrote:
Hi Kevin
It's impossible to debug invisible code (without loading the Telepathy module
:-), so posting it would help.
As for the forum, your description does not suggest a DBI problem, but rather a
general Perl problem. Hence I suggest the n
I'm not sure if this is the right forum so i'd appreciate pointers to
the correct place if i'm wrong.
I've got DBI running between apache and an Oracle 10gR2 database. I can
insert data with no problem. Here's what i'm attempting to do.
1. Put up a HTML form where user enters his userid, pa
Why don't you use DBD::Pg?
perl -MCPAN -e "install 'DBD::pg'"
Alexander
On 12.06.2006 16:24, [EMAIL PROTECTED] wrote:
Running perl 5.8.1 (multi-thread - beyond my control) on SUSE 9.2.
DBI is 1.48. DBD::Oracle works OK. Am attempting to get ODBC
working in order to connect to Progress Data
Running perl 5.8.1 (multi-thread - beyond my control) on SUSE 9.2.
DBI is 1.48. DBD::Oracle works OK. Am attempting to get ODBC
working in order to connect to Progress Database. ODBC drivers
(with appropriate Progress license) installed; Progress
version 9.1E. The PROGRESS/UNIX/ODBC drivers a
Hi,
DBI documentation says execute on a an active statement should imply a finish
call but DBD::DB2 does no appear to do this - see example below.
This issue is now causing me a severe amount of grief as we have no finish
calls anywhere in our code and we are finding more and more cases where fin
(I don't like cross posting so my reply is restricted to dbi-users)
On 12-Jun-2006 Steve Hay wrote:
> Patrick Galbraith wrote:
>> * To turn off server-side prepare statements to have emulated prepared
>> statements, append ";mysql_emulated_prepare=0" in the connect string or
>> via the driver hand
Patrick Galbraith wrote:
* To turn off server-side prepare statements to have emulated prepared
statements, append ";mysql_emulated_prepare=0" in the connect string or
via the driver handle.
Shouldn't that be ";mysql_emulated_prepare=1" ?
Also, I see that as of 3.0004_1 UTF-8 support has been
Hi Dean,
thanks that sounds promising, I'll give it a try.
Many many thanks
Tom
Dean Arnold schrieb:
>>
>> On 10.06.2006 14:58, Tom Schindl wrote:
>>
>>> Hi,
>>>
>>> I read the POD of DBD::ODBC but there's only the commercial from
>>> http://www.openlinksw.com mentionned, isn't there an open ve
Hi Alexander,
yeah that was my first idea the customer came to me but it's not
possible because the Win-Server is not under my control and the other
side is not willing to install anything onto their system.
Tom
Alexander Foken schrieb:
> Did you think about using DBD::Proxy on Linux and ActiveP
13 matches
Mail list logo
