Laszlo Hornyak wrote:
IMHO this is why decoupling is good and neccesary. If one configures the RDBMS to use different another of data, then I simply replace a couple of lines in the data mapping configuration. In the case of custom datatypes in PostgreSQL, the same happens. This is no code modification nor recomplitation in PL-J, only a reconfiguration.
This is why I have sent that link, but this configuration file fragment may explain it better:
<typemapper>
<map>
<type db="timestamp" class="org.pgj.typemapping.postgres.PGTimestamp"/>
<!-- type db="timestamp" class="org.pgj.typemapping.postgres.PGTimestampINT64"/ -->
Sure Laszlo. That solves everything. But where do you get the information on what to comment out and what to use in the first place?
Regards, Thomas Hallgren
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
