in reply to DBD::ODBC and binding to a money column

I've always been frustrated when having to deal with ODBC connections myself. It looks like if you are going to continue using MS-SQL you're going to have to deal with workarounds such as this.

<open source pitch>

I would highly recomment switching to PostgreSQL, or one of the other excellent open source databases, but it's understandable if that option isn't feasible for various reasons. Although if you had this same problem with an open source database, you can just go in the source and fix it instead of having to wait 4 years and continue work arounds.

</open source pitch>

  • Comment on Re: DBD::ODBC and binding to a money column

Replies are listed 'Best First'.
Re^2: DBD::ODBC and binding to a money column
by jfroebe (Parson) on Dec 16, 2004 at 16:11 UTC
    It's not actually a bug in the odbc driver or in the DBD::ODBC module. The money datatype is in truth a float. It is not unusual to explicitly state the datatype as Michael Peppler wrote in another reply. This 'issue' is a non-issue ... it is probably preferrable to state the datatype when binding a column if the datatype is known.

    Switching DBMSs (opensource or commercial) is overkill. I won't get into the whole opensource vs commercial dbms's as it really isn't relevant here.

    Jason L. Froebe

    Team Sybase member

    No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil, Stargate SG-1