Skip to main content
Question

How to change PostGIS Reader varchar width on certain fields

rudystricklan1
Contributor
Forum|alt.badge.img+2

I'm reading a PostGIS database layer that is formatted as 'Text'. PostGIS treats this as basically an unlimited-width VARCHAR field. However, the FME PostGIS Reader truncates this field's input to 80 characters, and I can't get it to change to accommodate more characters.

2 replies

M
Forum|alt.badge.img+2

@rudystricklan1​ I haven't been able to reproduce your issue in FME 2021 using the following example data:

CREATE TABLE longtext
(
    longtext text ,
    longvarchar character varying(150) ,
    longchar character(150) 
);
 
insert into longtext values ('123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*',
							 '123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*',
							'123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*');

When I read this data back in FME the 'text' field reads all 120 characters.  Perhaps you can use this small example to replicate your problem and then we can chase down the cause.

rudystricklan1
Contributor
Forum|alt.badge.img+2
markatsafe wrote:

@rudystricklan1​ I haven't been able to reproduce your issue in FME 2021 using the following example data:

CREATE TABLE longtext
(
    longtext text ,
    longvarchar character varying(150) ,
    longchar character(150) 
);
 
insert into longtext values ('123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*',
							 '123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*',
							'123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*123456789*');

When I read this data back in FME the 'text' field reads all 120 characters.  Perhaps you can use this small example to replicate your problem and then we can chase down the cause.

Thanks, Mark. Actually, the solution was to change the *writer* parameter to 150. It seems odd that it isn't the PostGIS Reader parameters that control the amount of data read in per field. Please make this issue as solved!

Rudy Stricklan

Reply


Helpful Members This Week

Community Stats

31,316
Posts
118,810
Replies
38,946
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.