On 2011-04-22, Geoffrey Myers g...@serioustechnology.com wrote:
Vick Khera wrote:
On Fri, Apr 22, 2011 at 11:00 AM, Geoffrey Myers
li...@serioustechnology.com mailto:li...@serioustechnology.com wrote:
Here's our problem. We planned on moving databases a few at a time.
Problem is,
Jasen Betts wrote:
On 2011-04-22, Geoffrey Myers g...@serioustechnology.com wrote:
Vick Khera wrote:
On Fri, Apr 22, 2011 at 11:00 AM, Geoffrey Myers
li...@serioustechnology.com mailto:li...@serioustechnology.com wrote:
Here's our problem. We planned on moving databases a few at a time.
Geoffrey Myers li...@serioustechnology.com writes:
So, now the question is, is this effort even worth our effort?
What is the harm in leaving our databases SQL_ASCII encoded?
You're declaring bankruptcy on being able to make any sense of the data
you stored. Is that really what you think you
We are moving our databases to new hardware soon, so we felt it would be
a good time to get the encoding correct. Our databases are currently
SQL_ASCII and we plan to move them to UTF8.
So, as previously noted, there are certain characters that won't load
into a UTF8 database from a dump of
On Fri, Apr 22, 2011 at 11:00 AM, Geoffrey Myers
li...@serioustechnology.com wrote:
Here's our problem. We planned on moving databases a few at a time.
Problem is, there is a process that pushes data from one database to
another. If this process attempts to push data from a SQL_ASCII
On Friday, April 22, 2011 8:00:08 am Geoffrey Myers wrote:
What is the harm in leaving our databases SQL_ASCII encoded?
SQL_ASCII is basically no encoding. The world is slowly but surely moving to
Unicode, sooner or later you are going to hit the unknown encoding/Unicode
wall.
Probably
On Fri, Apr 22, 2011 at 11:16 AM, Geoffrey Myers g...@serioustechnology.com
wrote:
Totally agree. Still, the question remains, why not leave it as SQL_ASCII?
you have no guarantees that the data stored within is utf-8. that is all.
if you can make such guarantees from within your
Vick Khera wrote:
On Fri, Apr 22, 2011 at 11:00 AM, Geoffrey Myers
li...@serioustechnology.com mailto:li...@serioustechnology.com wrote:
Here's our problem. We planned on moving databases a few at a time.
Problem is, there is a process that pushes data from one database to
On 04/22/2011 09:16 AM, Geoffrey Myers wrote:
Vick Khera wrote:
On Fri, Apr 22, 2011 at 11:00 AM, Geoffrey Myers
li...@serioustechnology.com mailto:li...@serioustechnology.com wrote:
Here's our problem. We planned on moving databases a few at a time.
Problem is, there is a process that
On Fri, Apr 22, 2011 at 9:16 AM, Geoffrey Myers
g...@serioustechnology.comwrote:
Vick Khera wrote:
The database's enforcement of the encoding should be the last layer that
does so. Your applications should be enforcing strict utf-8 encoding from
start to finish. Once this is done, and the
On 04/22/2011 08:00 AM, Geoffrey Myers wrote:
We are moving our databases to new hardware soon, so we felt it would
be a good time to get the encoding correct. Our databases are
currently SQL_ASCII and we plan to move them to UTF8.
We are in the same boat, fortunately only on one older server
11 matches
Mail list logo
