On 2011-01-24, Geoffrey Myers li...@serioustechnology.com 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
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:
pg_restore: [archiver (db)] Error while PROCESSING TOC:
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:
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
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
are
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
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 as they were
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
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 reload
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
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
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
12 matches
Mail list logo
