Mercurial Monks,
I'm having a little trouble with accessing an old DBM file using DBI.
We have an old DBM file:
data.pag
data.dir
I simply want to see what's in it. Thought the DBI would be a good way, so:
#!/usr/bin/perl -w
use strict;
use warnings;
use DBI;
use CGI;
use CGI::Carp qw(fatalsToBrowser);
# start error output
BEGIN {
use CGI::Carp qw(carpout);
carpout(*STDOUT);
}
print "Content-type:text/html\n\n";
my $db_name = 'data';
my $dbh = DBI->connect('dbi:DBM(RaiseError=1):');
my $sqlSelect = "SELECT * FROM $db_name";
my $sth = $dbh->prepare($sqlSelect) || die "Cannot prepare: " . $dbh->
+errstr();
$sth->execute() or die "Cannot execute: " . $sth->errstr();
while (my @data = $sth->fetchrow_array()) {
print "<br>";
for my $i (0 .. $#data) {
print ", $data[$i]\n";
}
}
$sth->finish;
But what I get is
Software error:
DBD::DBM::st execute failed:
Execution ERROR: No write permission to sdbm file at /bla/bla/bla/DBD/
+DBM.pm line 422.
.
at /bla/bla/bla/DBI/DBD/SqlEngine.pm line 1234.
[for Statement "SELECT * FROM pmb_passwords_dbm"] at dumpmydbm.pl lin
+e 26.
For the record - both the files are chmod'd 755.
Now, I was previously getting the error "no lck file" - so I simply created an empty data.lck file and that seemed to shut that up.
What's up?
Thanks.
Time flies like an arrow. Fruit flies like a banana.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|