Hi Roland,
Interesting thread, this one.
But indeed, even if you succeed and we get you a transformer that
renames the attributes into their lower case equivalents, that only
affects the actual data going by. At the end (or the beginning) of
the day, you need to define your PostGIS tables, and that definition
is where you need the lower casing I think. So you really don't need
the attributes themselves renamed as much as you need the definition
to have lower case attribute names, the defintion of the output
PostGIS table column names. And then FME would have to be told to map
the upper case attributes to their lower case destinations (which an
auto-link already does).
So what I'm thinking we should do to solve this is just add a settings
box option for PostGIS that says "lower case column names", and if
this is ticked to say YES, then we'd do what we used to, and perhaps
all would be well?
Dale
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/fme/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/fme/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
