in reply to Re^2: sth->execute returns undef when successful
in thread sth->execute returns undef when successful

Ouch. No personal bias, I am not one of those anti-thread boogeymen, and I tried to preface my comment appropriately, asking questions, not making statements. What do you think the problem is?

The way forward always starts with a minimal test.

Replies are listed 'Best First'.
Re^4: sth->execute returns undef when successful
by BrowserUk (Patriarch) on Aug 08, 2015 at 19:50 UTC
    What do you think the problem is?

    I really have no idea, hence why I've not posted.

    From the trace it looks like the call to the db completed successfully: "dbd_st_execute CREATE returned (SUCCESS, rpc2211750915, fn1, out0)" which probably points to a bug in the DBI/Oracle driver.

    I think the OP will need advice from a DBI/Oracle expert.

    Though I do wonder if this might have something to do with it:

    "For a non-SELECT statement, execute returns the number of rows affected, if known. If no rows were affected, then execute returns "0E0", which Perl will treat as 0 but will regard as true. Note that it is not an error for no rows to be affected by a statement. If the number of rows affected is not known, then execute returns -1."
    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
    In the absence of evidence, opinion is indistinguishable from prejudice.
    I'm with torvalds on this Agile (and TDD) debunked I told'em LLVM was the way to go. But did they listen!
[reply]

In Section Seekers of Perl Wisdom