Maybe a bug: Reading double precision columns from a PostgreSQL Table

[Sparhawk]

I found a workaround... Using a cast on the postgresql query to varchar:

select cast(coste as varchar), cast(pvp as varchar) from foo ...

Now it works.