Type double does not exist on Postgres

[yaghmr]

Hi,
I have a class like this

case class Geocoding(city: String, latitude: Double, longitude: Double)

and this SORM initialization:

object Db extends Instance (
  entities = Set(
    Entity[Geocoding](unique = Set() + Seq("city", "latitude", "longitude"), indexed = Set() + Seq("city") + Seq("latitude", "longitude")),
  url = "jdbc:postgresql://localhost:5432/common_data",
  initMode = InitMode.Create,
  poolSize = 20
)

using Postgresql (driver version: 9.1-901.jdbc4)
SORM try to create the table with this SQL code:

| CREATE TABLE "geocoding"  
|   ( "id" BIGSERIAL NOT NULL,
|     "longitude" DOUBLE NOT NULL,
|     "latitude" DOUBLE NOT NULL,
|     "city" VARCHAR(255) NOT NULL,
|     PRIMARY KEY ("id"),
|     UNIQUE ("city", "latitude", "longitude") )

with version <= 0.3.8 the geocoding table is not create silently
with version 0.3.13 i get

java.lang.ExceptionInInitializerError: null
...
Caused by: org.postgresql.util.PSQLException: ERROR: type "double" does not exist

The error is caused by "DOUBLE" type,
Postgres have instead "DOUBLE PRECISION" type.

[nikita-volkov]

Thanks for the report. Fixed in 0.3.15.

[zarinfam]

We use Slick 3.1 and it generate wrong create statements for Double PostgreSQL column, it generate DOUBLE instead of double precision !

[aguestuser]

seeing the same problem as @zarinfam any suggestions?

[aguestuser]

nevermind! resolved our issue.

@zarinfam: one possible gotcha that tricked us up and you might want to watch out for -- the source of our bug was namespace collisions between an import of slick's H2 DSL (import slick.driver.H2Driver.api._) and its Postgres driver (import slick.driver.PostgresDriver.api._) which caused calls to column[Double] in our Table declaration code to pick up on H2Driver.api's notion of Doubles rather than PostgresDriver.api's. Not sure if this might be the cause of your bug, but perhaps worth a quick sanity check just to make sure?

[zarinfam]

@aguestuser You were right and the bug was for namespace collisions. thanks.

[willemvermeer]

Thanks @aguestuser made the same mistake today - thanks for reporting back the root cause.