ok I've tried this again and have some interesting results. I used pgAdmin's migration tool to try to move the data across - I created the pg database as unicode, and used the unicode option for the migration - and ended up with an error:
An error occured at: 29/01/2003 11:11:54 AM: -2147467259: ERROR: Invalid UNICODE character sequence found (0xee7472) I had actually forgotten, as it happened late at night but I got this same error when I tried on the weekend after creating a unicode database... Any ideas? I can only assume that either there's some weird character gone in through a copy and paste from msword to the website textbox used for input, as Paul suggested, or CF4/5 has saved bad unicode in there and now I'm stuck with it. how does one go about correcting something like this? Toby Wednesday, January 29, 2003, 10:35:31 AM, you wrote: TT> Hi Jochem, jotn>> What charset is this data using? TT> ach - just whatever the default is for cf 4.0 /4.5 (UTF-8?) There TT> were no processing directives or locale settings in the app at all. TT> It's been running on a windows machine (NT) up to now. jotn>> If the data in Access is visible correctly when using Access it self it is not a jotn>> normal unicode issue. TT> that's what I figured - I can view the data in access, and cf 4.5 / TT> 5.0 seems to pull it out of access fine (I haven't had the chance to TT> try it on windows with cfmx yet). And over the weekend I tried TT> postgres Manager which pulled the data out fine as well (from the TT> postgres DB on the linux machine). jotn>> Which CF version did you use to move the data? Which client_encoding did you set jotn>> in PostgreSQL during the migration? Did you set up the PostgreSQL database to jotn>> use unicode (WITH ENCODING 'UNICODE')? Can't you use the pgAdmin database jotn>> migration wizard to move the data from Access to PostreSQL and then use built-in jotn>> functionality to transform the data? TT> initially I used cf 5 on windows to move the data to the postgres db TT> on the linux machine. The linux box is running cfmx, and that's where TT> I'm seeing the dodgy characters. On the weekend I tried doing the TT> same transfer with cfmx on windows instead of cf5 and strangely enough TT> it didn't fix it completely but it did end up with LESS dodgy TT> characters in the display on the linux machine. TT> I initially hadn't done anything special with character encoding for TT> postgreSQL, but in the above test I recreated the postgreSQL database TT> using WITH ENCODING = 'UNICODE' and nothing changed. TT> I haven't tried the pgAdmin migration wizard actually, last time I TT> used pgAdmin I don't think it had the migration wizard. I've been TT> using a script as I also needed to transform a lot of the data to new TT> table stuctures (the old one is a complete mess). I'll try with TT> pgAdmin and see how I go. TT> Thanks for the tips Jochem, I'll test your advice and post back. TT> cheers, TT> Toby jotn>> Jochem jotn>> TT> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
