in reply to Re^2: DBI and bind_columns again
in thread DBI and bind_columns again

Are you sure all values were indeed correctly inserted? My first guess would be that the port and country fields are empty in your database.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

Replies are listed 'Best First'.
Re^4: DBI and bind_columns again
by gemoroy (Beadle) on May 01, 2009 at 11:05 UTC
    "Are you sure all values were indeed correctly inserted? My first guess would be that the port and country fields are empty in your database." May be you are right...but why? Query likely to be correct stated..and i think Insert query should return errstr in such situation, should'nt it?
[reply]
      i think Insert query should return errstr in such situation, should'nt it?
      It should, but there is nothing guaranteed. All depends on the database and the DBI and DBD implementation.

      I never used the DBM database (strictly MySQL or SQLite here) but I read in the DBD::DBM docs that "out-of-the-box" it only supports tables with two columns, unless you specifically require the multi-column version. Maybe that is where the problem is coming from?

      CountZero

      A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

[reply]
        I think you are exactly right i've re-read DBM docs to, i should use MLDBM to use more than two columns. Thanks a lot!!
[reply]

In Section Seekers of Perl Wisdom