The PostgreSQL JDBC driver will "toString" the monetary amount, which
produces a locale-dependent value. This is hard to parse back again into
jOOQ's current BigDecimal mapping. Will need to think about this a bit more
thoroughly. Further discussion directly on the issue #6850
The decimal precision is fixed by the server's relevant lc_monetary
setting, but what if that setting changes? Will we lose precision,
suddenly? What if we're in Switzerland (0.## precision) but we want to
trade with stocks (often usually 0.#### precision)? Is it still an
Given that not even the JDBC driver correctly handles the money type after
a simple test (pardon my German):
org.postgresql.util.PSQLException: Unzulässiger Wert für den Typ double :
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to [hidden email].