On Tue, 29 Jul 2003 16:05:39 -0500 "Galbraith, Mark" <[EMAIL PROTECTED]> wrote:
> I have been asked to call a stored procedure, and then use the value
> stored in a variable inside the package. I've looked at the
> documentation, including the appropriate chapters in Programming The
> Perl DBI (O
On Tue, 29 Jul 2003 20:19:35 -0400, [EMAIL PROTECTED] wrote:
>I noticed the same problem and recently had to revert back to 1.005
You mean 1.004, yes?
>myself. The 1.005 version was choking on simple statements like:
>
>UPDATE table
>SET name='your_name',value='your_value'
>WHERE id<>''
>
>In 1.
I noticed the same problem and recently had to revert back to 1.005
myself. The 1.005 version was choking on simple statements like:
UPDATE table
SET name='your_name',value='your_value'
WHERE id<>''
In 1.004 this worked fine. In 1.005 no updates occurred. This was
also the case for SELECT stat
There's no reason you can't use bind_param_inout for arguments to a
procedure - I do it all the time. Did you encounter any specific
problem?
-Original Message-
From: Galbraith, Mark [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 30 July 2003 7:06 AM
To: [EMAIL PROTECTED]
Subject: Getting va
Perl 5.6.1, DBI 1.37, DBD::CSV 0.2002, SQL::Statement 1.005.
Once I upgraded to this combination of modules, my previously working program stopped
doing so. In order to solve the problem, I had to drop back to the last known working
version of
SQL::Statement - 0.1016.
The problem was that I ha
I have been asked to call a stored procedure, and then use the value stored in a
variable inside the package. I've looked at the documentation, including the
appropriate chapters in Programming The Perl DBI (O'Reilly).
I found that by changing the procedure to a function, I can call the functio
On 29 Jul 2003 at 22:44, Bart Lateur wrote:
> So MySQL cares now, does it? I'm still on MySQL 3.x, and I know that
> there you may quote any type of field, so "123" for an inetegr is
> alright.
The issue is specific to the values after "LIMIT". Strings in most
other places are converted to inte
R. Steven Rainwater wrote:
But with DBD::CSV, it seems to be converting each newline
newline character in the literal characters slash and n,
Hmm, I wonder why I never noticed that or no one reported it. I'll
investigate for the next release. Two quick fixes: change the code to
use placeholder
On Tue, Jul 29, 2003 at 05:01:40PM -0400, JT MacNeil wrote:
> Check the permissions on DBI.pm. They should be 664.
>
Also check the permissions on the directories in /usr/lib/whatever.
Ronald
Jonathan Leffler wrote:
Rasoul Hajikhani wrote:
Jonathan Leffler wrote:
Rasoul Hajikhani wrote:
Here is a brief description of my DBD::Informix
Type: dr
Name: Informix
Version: 2003.04
Attribution: Jonathan Leffler <[EM
I've got a Perl DBI application that's working fine with
MySQL and PostgreSQL. Now I'm trying to add support for
CSV files using the DBD::CSV modules.
I've run into a problem with storing text that contains
embedded newslines or returns. With the real SQL DBs, I
just do something like dbh->quote
Check the permissions on DBI.pm. They should be 664.
J-T MacNeil
Design Team Member, Connect 24 Division
Digital Security Controls
Phone: (905) 760-3000 x7318
e-Mail: [EMAIL PROTECTED]
> -Original Message-
> From: Raymond Chui [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 29, 2003 1:37
Hi,
I'm trying to build DBD-Oracle-1.14 on a Windows 2000 machine with
Oracle 9.2.0.1.0 Standard installed. I should also point out that I'm
working within a unix environment (a product called Microsoft Windows
Services for Unix) which runs under Windows and I'm trying to install
DBD into the
My OS is Redhat Linux 7.2
My database is PostgreSQL 7.1.3
I have success installed DBI 1.3.7 and DBD-Pg 1.2.2
with out any problem.
I created a testDBI.pl file contains two lines
#!/usr/bin/perl -w
use DBI;
When I execute this file, I got
Can't locate loadable object for module DBI in @INC (@INC
On 29 Jul 2003 19:08:23 +0100, Dan Rowles wrote:
>2) Does anyone know if there's a way of getting the DBI to revert to
>it's old behaviour of not automatically quoting placeholder-values?
So MySQL cares now, does it? I'm still on MySQL 3.x, and I know that
there you may quote any type of field,
On 29 Jul 2003 19:08:23 +0100, Dan Rowles wrote:
>To go through and change all of these methods to do a
>"$sth->bind_param(n, $val, SQL_INTEGER)" is a lot of work!
Er, you don't have to. It's the first occurrence of using a value for
some placeholder that defines how it'll be used further on. So
On 29 Jul 2003, Dan Rowles wrote:
> My problem is that I have a large code-base already installed that uses
> the "$sth->execute(@args)" way of parsing in placeholder values. This
> used to work fine. To go through and change all of these methods to do a
> "$sth->bind_param(n, $val, SQL_INTEGER)"
Making progress on the DBI:Proxy path. I am currently getting the
following errors from the output...
DBI handle cleared whilst still active at ./space_data.pl line 20.
dbih_clearcom (sth 0x4025172c 0x40251d20, com 0x40137878, imp
DBD::Proxy::st
):
FLAGS 0x115: COMSET Active Wa
On 29 Jul 2003 19:08:23 +0100 Dan Rowles <[EMAIL PROTECTED]> wrote:
> My problem is that I have a large code-base already installed that uses
> the "$sth->execute(@args)" way of parsing in placeholder values. This
> used to work fine. To go through and change all of these methods to do a
> "$sth->
Dear Scott et al -
> "SCOTT" == SCOTT V NIPP writes:
SCOTT> I am developing a series of scripts to collect system
SCOTT> information on a fairly large number of HP-UX servers.
Use SNMP to gather the information remotely and then send the information
to a remote MySQL. Then your sc
Hi Paul,
Thanks for your input.
My problem is that I have a large code-base already installed that uses
the "$sth->execute(@args)" way of parsing in placeholder values. This
used to work fine. To go through and change all of these methods to do a
"$sth->bind_param(n, $val, SQL_INTEGER)" is a lo
At 16:20 +0100 7/29/03, Dan Rowles wrote:
Hi there,
I'm using MySQL 4.0.13-standard, DBD-mysql 2.9002, DBI 1.37, perl 5.6.1
AND perl 5.8.0.
The attached program causes a crash, with the following error statement
in both version sof perl. It used to work fine using MySQL 3.23.x, and
older versions
Hey all... I am developing a series of scripts to collect system
information on a fairly large number of HP-UX servers. Initially, this
system information is fairly limited to filesystem information but will be
expanded over time to include other things like kernel parameter settings,
use
Also learn about CPAN. Either
'cpan'
or
'perl -MCPAN -e shell'
will get you to the CPAN shell. It will ask you to configure it; be sure to use the
suggested
UNINST=1
in the make parameters if you are installing as root, as this prevents (in most cases)
multiple copi
Hi there,
I'm using MySQL 4.0.13-standard, DBD-mysql 2.9002, DBI 1.37, perl 5.6.1
AND perl 5.8.0.
The attached program causes a crash, with the following error statement
in both version sof perl. It used to work fine using MySQL 3.23.x, and
older versions of the DBI.
bash-2.05a$ ./database.pl 1
Derek,
The best place to find what you are looking for in DBI is
http://dbi.perl.org/, this will give you a basis of what it is all about. I
have been using the interface for about 6 months and love it.
Jared
-Original Message-
From: Derek Byrne [mailto:[EMAIL PROTECTED]
Sent: Tuesday, J
Hello, can you help me?
I lost 3 days but can not find how to fix a BIG PROBLEM.
So, I have IIS 5.0 and Windows 2000 Professional.
I install Active Perl and goes for DBD::mysql
So, log:
--
Microsoft Windows 2000 [Version 5.00.2195]
(C) C
At 11:57 28/07/03, Bart Lateur wrote:
Try to find out what compiler they used
perl -V should tell you
--
MarkT
=
E M Thornber CEng MIEE
Enchanted Systems Limited
Software Toolsmiths
+44 (0) 1503 272097
Hi,
I'm trying to access a Microsoft Access 2000 Database, with multiple
fields.
Unfortunately I'm a newbie on all fronts here (Perl, Access, ODBC, dbi).
I've created a system DSN to access the database file, and have created a
perl script or two to access both the complex and also a simple
29 matches
Mail list logo
