Thread: Re: Money type mapping to backend

Bill Hutto wrote:

> > Please send the "psqlodbc.log" file of the session.  This will show the sql statement
> > as sent to the backend and prove once and for all what the error is.  It is hard to
> > make a diagnosis without knowing what really is going wrong.
>
> OK Byron, I've attached the session using data bound controls from
> Visual Basic.
>
> Table Name: visdata
>
> Fields:
>         field1  char(40)
>         amount  money
>         quantity        int8
>
> If you need any other info, just let me know.
>
>

Hey, guess what, I was testing the whole time under Postgres 6.3 and it does not require the quotes
around money type!  Only postgres 6.4 requires the quotes!

That seems kind of weird.  Anyone got any comments?

In the meantime, do you have a 6.3 database laying around to try?

Byron

> Hey, guess what, I was testing the whole time under Postgres 6.3 and
> it does not require the quotes around money type!
> Only postgres 6.4 requires the quotes!
> That seems kind of weird.  Anyone got any comments?

That is a result of the "improvements" to the type coersion and
conversion I made for v6.4. The money type never had a full set of
explicit conversion functions to and from other types, but the old type
coersion/conversion scheme, which could only handle constants, would
brute-force convert the input value to a string and then try shoving it
through the target type input routine.

The new scheme can work with constants, columns, and expressions, but
there appears to be a hole in the available conversion functions for the
money type.

otoh, with the NUMERIC() and DECIMAL() types implemented by Jan, the
money type is completely and absolutely obsolete in the next release
afaik. Once we get these new types working on all platforms (I've got
troubles on my linux box; anyone else have success on non-BSD machines?)
we can think about a migration/compatibility strategy...

                   - Tom

> > Hey, guess what, I was testing the whole time under Postgres 6.3 and
> > it does not require the quotes around money type!
> > Only postgres 6.4 requires the quotes!
> > That seems kind of weird.  Anyone got any comments?
>
> otoh, with the NUMERIC() and DECIMAL() types implemented by Jan, the
> money type is completely and absolutely obsolete in the next release
> afaik. Once we get these new types working on all platforms (I've got
> troubles on my linux box; anyone else have success on non-BSD machines?)
> we can think about a migration/compatibility strategy...

I figure if the Numeric and Decimal types are coming pretty soon, I'm
probably going to wait and see how they work. If it works according
to my docs, the Numeric will map straight to the Jet's Currency
type (scaled integer), and hopefully there won't be any quote
problems. That would be perfect. Thanks for your help guys, nice
job, and I look forward to this upgrade.

Cheers,
Bill