Let me try to explain the issue again, now that I've worked through it a couple of
times. When you export a table from Access you can select the delimiter you want. I've
been using
semicolons because there were commas inside my tables. There also were a large number
of carrage returns because the table contained HTML. Any exported Access txt or csv
file also will
contain carrage returns at the end of each line no matter what you select. Neither the
PSQL "copy" command nor the PGAccess import utility will accept carrage returns
anywhere in the
file. This means they have to be eliminated. It is impossible to use a text editor to
automatically "replace" carrage returns because they are indistinguishable from
spaces. However, if
you know where they are, you can manually delete them with the backspace key. I have
detailed my experiences in a document posted on the Vancouver CFUG site here:
http://cfug-vancouver.com/postgresqlport.cfm
If anyone has some simple and elegant way to avoid this hassle, I'd love to see it.
I'm especially interested in a methodology in which Cold Fusion in Linux is used to
"insert data into
postgres". Sound like magic to me. :)
Frank Hilliard
Jason Brooke wrote:
> They would be ok in the postgres database - but Frank said the means by which
> he is importing the data, is using carriage returns as row delimiters - that's
> why I suggested doing a simple select * from the access database. then loop
> over the result set inserting the data into postgres from a cf script. It
> won't care about the carriage returns
>
> jason
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-linux%40houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_linux or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
