Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
First some comments which may not help your immediate problem, but they might...

If your connect fails, the error message will not be in $dbh->errstr, because $dbh will be undef. It WILL be in $DBI::errstr, but even easier would be to use RaiseError in the connect, then you could get rid of all the 'or die ...' clauses in the other DBI statement. You are, for instance, not checking for errors in the fetch.

And you don't need to finish() a statement handle if you're going to fetch all of the rows from it.

AutoCommit is supposed to be on by default, so you shouldn't need to explicitly commit() anything (and I don't see any inserts/deletes/updates that need committing anyway) unless you turn off AutoCommit.

And finally, for some actual help, have you tried NOT using placeholders (just quoting 'guppy' directly in the SQL statement), and does it work? If that doesn't work then maybe the problem is that what's in the database is not what you think it is.

Update: Also, you're using the old-style form of connect (or maybe its just wrong, I forget what the old style was like), which prevents use of attributes like RaiseError during the connect. Look at the docs, and use the correct form ('Oracle' does not belong in that last position, that I'm sure of).


In reply to Re: DBI placeholders by runrig
in thread DBI placeholders by randomblue

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (3)
As of 2022-12-08 20:05 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?