On 2006-04-12 13:25:49 -0500, Paul DuBois wrote:
On 4/12/06 13:03, Peter J. Holzer [EMAIL PROTECTED] wrote:
This just cost me a few hours of debugging, so I am posting it to spare
others:
The mysql client character set can be set to UTF-8 with:
$dbh-do(set character set utf8);
Actually when I fetch records from Database then I getting question marks
for arabic characters, so any one can help me to solve this issue.
my $dbh = DBI-connect(dbi:ODBC:sms, smser, smspassword)
|| die Can't connect to $DBI::errstr;
my $sth = $dbh-prepare( q{
select
DBD::ODBC does not support Unicode (and thus arabic characters) at all.
You may want to try my patch for DBD::ODBC: README file at
http://www.alexander-foken.de/README.unicode-patch.html , gzip
compressed patch at http://www.alexander-foken.de/unicode-patch.txt.gz .
If you use Oracle or
Hi,
I encountered this intermittent server error which I had been trying to
resolved :
*** 'd:\inetpub\wwwroot\S_script\Qdr\Reports\rpt_preview.plx' error
message at: 2006/04/12 21:08:23
DBD::ODBC::st execute failed: [Microsoft][ODBC SQL Server Driver][SQL
Server]Invalid column name
Your SQL statement in
d:\inetpub\wwwroot\S_script\Qdr\Reports\rpt_preview.plx line 99 contains
the column name DISP_MODFY_DT that does not exist in your database.
This is not a DBI problem, DBI is just reporting it. It is a problem
with your SQL statement, your Database and perhaps your connect
Tim Bunce wrote:
On Wed, Apr 12, 2006 at 04:33:39PM +0200, Dr.Ruud wrote:
Jeffrey Seger schreef:
perl -MData::Dumper -e' print Dumper @INC'
Alternative:
perl -MData::Dumper -e' print Data::Dumper-Dump([EMAIL PROTECTED], [qw(*INC)])'
Oi, why not much cleaner (code and output):
perl
JupiterHost.Net schreef:
Dr.Ruud:
Jeffrey Seger:
perl -MData::Dumper -e' print Dumper @INC'
Alternative:
perl -MData::Dumper -e' print Data::Dumper-Dump([EMAIL PROTECTED],
[qw(*INC)])'
Oi, why not much cleaner (code and output):
perl -MData::Dumper -e' print Dumper [EMAIL PROTECTED],
- Forwarded message from Tomas Karlsson [EMAIL PROTECTED] -
I would like to suggest a new feature/function in DBI. It would really
be nice if there was a way to print out the actual sql statement for
debugging purpose, in particular in cases with placeholders like this
example:
It's been a long time since I've actively written Perl (and DBI) code, but I
wanted to add that IIRC if you use trace (or $dbh-trace(2) or trace(3) ??)
around the DBI code in question, the trace output includes(?) the SQL along
with the placeholder values being inserted. Hope I'm not mistating
We have a requirement here that we can't hard code any oracle database
instance name for security reasons. Is there any way we can pass the
connection string (for example, the oracle tnsname alias), or put the
instance name in a configuration file and somehow pass the information
from the
We have a requirement here that we can't hard code any oracle database
instance name for security reasons. Is there any way we can pass the
connection string (for example, the oracle tnsname alias), or put the
instance name in a configuration file and somehow pass the information
from the
Create your own module as exporter, db.pm for example, like something below.
Place the file in any location specified in @INC, then call it in the perl
program use db;.
package db;
BEGIN {
use Exporter();
@ISA = qw(Exporter);
@EXPORT = qw( $oUser $oPass $oString);
}
If the public can see your code, they also can see where the
configuration file is stored and how it is parsed. Nothing gained if
they have read access to the configuration file.
Think about using DBD::Proxy to connect to a proxy server running on a
separate, well protected machine that
On 13.04.2006 16:42, Luke Bakken wrote:
How can you do that in other languages?
Good question.
If you have strings in the
executable file, they can be discovered.
They could be encrypted, using something trivial like rot13 or xor, or
even good encryption algortihms like 3DES, blowfish,
On 13-Apr-2006 Hardy Merrill wrote:
It's been a long time since I've actively written Perl (and DBI) code, but I
wanted to add that IIRC if you use trace (or $dbh-trace(2) or trace(3)
??)
around the DBI code in question, the trace output includes(?) the SQL along
with the placeholder values
On 2006-04-13 09:59:02 -0400, Linda Ding wrote:
We have a requirement here that we can't hard code any oracle database
instance
name for security reasons.
[...]
my $dbh = DBI-connect( 'dbi:Oracle:orcl',
'jeffrey',
'jeffspassword',
On 2006-04-13 17:01:25 +0200, Alexander Foken wrote:
On 13.04.2006 16:42, Luke Bakken wrote:
If you have strings in the executable file, they can be discovered.
They could be encrypted, using something trivial like rot13 or xor, or even
good encryption algortihms like 3DES, blowfish, etc.,
I think we can probably end this thread now. If I hadn't been so
tiredit was the middle of the night...I'd have just had him run perl -V
to get his @INC arrary. Cleaner than any of this.
On 4/13/06, Dr.Ruud [EMAIL PROTECTED] wrote:
JupiterHost.Net schreef:
Dr.Ruud:
Jeffrey Seger:
Hi , I've had a problem when I try to run the perl -Mblib t/50cursor.t in DBD-ORACLE 1.16. It just creates a core on the 8th test.I've
tried 1.17 also and had the same problem so I've no idea what the
problem could be, so I just thought I'd post here to see if it's
something obvious.
I've included
Hi ,
I've had a problem when I try to run the perl -Mblib t/50cursor.t in
DBD-ORACLE 1.16. It just creates a core on the 8th test.
I've tried 1.17 also and had the same problem so I've no idea what the
problem could be, so I just thought I'd post here to see if it's
something obvious.
I've
Hi
I am in the process of migrating a web application from a small linux server
(Fedora 2, AMD processor), to a new larger box running RHEL 4, AMD64.
The version of postgres (8.1.3), DBD::Pg(1.47) and everything else (data and
application) is the same.
However, on the new server, two reports
Hi,
Trying to install DBD-ODBC 1.13 with iODBC manager installed on Mac
OSX 10.4
When pointing the Makefile.PL to the iODBC manager I get the error
that it does not recognize the manager.
When poking around a bit it looks like the simple i in iODBC is the
culprit.
Ulf Asplund
[EMAIL
Please disregard my comment in earlier email.
I still can not make it work but it was not as simple as I voiced
earlier.
Sorry about that.
Ulf Asplund
[EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ERROR: prepared statement dbdpg_1 does not exist
The two reports have multiple cursors (3 levels) and have never had a problem
before. I have error checked the cost, and there are no errors prior to
calling 'execute', but the execute fails
On Thu, 13 Apr 2006 17:46:00 +0200, Peter J. Holzer wrote:
Hi Peter
$store-init(credential_file =
'/var/lib/www/offline/webmail/dbi/connect_data');
And if for some reason you put the config file in a directory from which the
client can run scripts, i.e. alongside *.cgi, you can call the file
25 matches
Mail list logo
