On 2011-01-24, Geoffrey Myers wrote:
> Adrian Klaver wrote:
> Thanks for the suggestion. As it stands, we are getting different
> errors for different hex characters, thus the solution we need is the
> ability to identify the characters that won't convert from SQL_ASCII to
> UTF8. Is there a
On 01/24/2011 10:57 AM, Geoffrey Myers wrote:
Adrian Klaver wrote:
On 01/24/2011 09:16 AM, Geoffrey Myers wrote:
We hope to identify the characters and fix them in the existing
database, then convert. It appears to be very limited, but it would help
if there was some way to identify these cha
Adrian Klaver wrote:
On 01/24/2011 09:16 AM, Geoffrey Myers wrote:
We hope to identify the characters and fix them in the existing
database, then convert. It appears to be very limited, but it would help
if there was some way to identify these characters outside of simply
doing the reload of t
On 01/24/2011 09:16 AM, Geoffrey Myers wrote:
We hope to identify the characters and fix them in the existing
database, then convert. It appears to be very limited, but it would help
if there was some way to identify these characters outside of simply
doing the reload of the data and finding th
On Mon, Jan 24, 2011 at 12:16:46PM -0500, Geoffrey Myers wrote:
> We hope to identify the characters and fix them in the existing
> database, then convert. It appears to be very limited, but it would
> help if there was some way to identify these characters outside of
> simply doing the relo
Adrian Klaver wrote:
On Monday 24 January 2011 8:06:38 am Geoffrey Myers wrote:
Adrian Klaver wrote:
On Monday 24 January 2011 7:57:52 am Geoffrey Myers wrote:
Adrian Klaver wrote:
On Monday 24 January 2011 6:38:55 am Geoffrey Myers wrote:
We need to change the database encoding on our datab
On Monday 24 January 2011 8:06:38 am Geoffrey Myers wrote:
> Adrian Klaver wrote:
> > On Monday 24 January 2011 7:57:52 am Geoffrey Myers wrote:
> >> Adrian Klaver wrote:
> >>> On Monday 24 January 2011 6:38:55 am Geoffrey Myers wrote:
> We need to change the database encoding on our databases
Adrian Klaver wrote:
On Monday 24 January 2011 7:57:52 am Geoffrey Myers wrote:
Adrian Klaver wrote:
On Monday 24 January 2011 6:38:55 am Geoffrey Myers wrote:
We need to change the database encoding on our databases as they were
created with the wrong encoding. They were created as SQL_ASCII
On Monday 24 January 2011 7:57:52 am Geoffrey Myers wrote:
> Adrian Klaver wrote:
> > On Monday 24 January 2011 6:38:55 am Geoffrey Myers wrote:
> >> We need to change the database encoding on our databases as they were
> >> created with the wrong encoding. They were created as SQL_ASCII and we
>
Adrian Klaver wrote:
On Monday 24 January 2011 6:38:55 am Geoffrey Myers wrote:
We need to change the database encoding on our databases as they were
created with the wrong encoding. They were created as SQL_ASCII and we
are changing them to UTF8.
When testing this Friday, I received the follo
On Monday 24 January 2011 6:38:55 am Geoffrey Myers wrote:
> We need to change the database encoding on our databases as they were
> created with the wrong encoding. They were created as SQL_ASCII and we
> are changing them to UTF8.
>
> When testing this Friday, I received the following error:
>
>
11 matches
Mail list logo
