Double Precision results in unusual length

Classic Servoy
1

Hi,

I’m using Postgres with Servoy 7.4.1.
When I create a table in pgadmin, with a column double precision
CREATE TABLE test2
(
test_id character varying(36) NOT NULL,
test_number_field double precision,
CONSTRAINT test_pkey PRIMARY KEY (test_id)
)
WITH (
OIDS=FALSE
);
ALTER TABLE test2
OWNER TO “DBA”;

Then when I go to Servoy in the data base servers, and open the table (test2), I see the column test_number_field as having type Number and length 1717.
Can someone please explain why the length is this way?

Is there a way to avoid this situation?

Regards,
Hareendra

2

Rob from Servoy Support told me that the length information “17,17” is show when Servoy imports a NUMBER type from postgreSQL, so it’s nothing to worry about.
This is information that was reported by the driver, it is not related to the length of the field or its precision.
I conclude that Servoy uses the length column of its table editor to also show type information of imported types.