Hello Tim, Hmm, if Firebird allows you to store such characters, I would expect Database Workbench to support it. ;)
If you can find a reproducible case, let me know. With regards, Martijn Tonies Upscene Productions http://www.upscene.com Download Database Workbench for Oracle, MS SQL Server, Sybase SQL Anywhere, MySQL, InterBase, NexusDB and Firebird! From: Tim Ward Sent: Friday, April 25, 2014 10:27 AM To: [email protected] Subject: Re: [firebird-support] non us characters in comments fail I'm using v4.4.5.0. I can't check what others are using as they aren't in the office just right now, but I would expect them to be on the same version. On 25/04/2014 09:23, Martijn Tonies (Upscene Productions) wrote: Hello Tim, >Yes, I had one of these yesterday - part of a comment had been >cut-and-pasted from Word, and contained something that looked like an >ASCII minus but was in fact an em-rule. > >Whether you get a failure or not, and at which point of the process, >depends, apparently, on all sorts of things, including in particular the >connection character set. In our case the procedure had been stored in >the database OK, and the application ran OK, but developers couldn't >extract metadata from the database using Database Workbench or (to a >more limited extent) FlameRobin. Are you still experiencing this issue with recent versions of Database Workbench?
