public marks

PUBLIC MARKS with tags migration & mysql

2017

2016

2008

2007

Mysql database migration and special characters | Orthogonal Thought

by kasi77 & 2 others (via)
So, I keep having all sorts of problems when moving my mysql database from one machine to another. The issue is that in text or varchar columns containing data that have special characters like smart quotes (those crazy curly quotes), accented letters, etc. result in scrambled data. For

2006

Mike Kruckenberg: Guide to Incompatibilities when Upgrading MySQL to Version 5.0

by mbertier & 1 other
Here are the items from the MySQL 5.0 release notes that are marked Warning: Incompatible change:

Mike Kruckenberg: Guide to Incompatibilities when Upgrading MySQL to Version 4.1

by mbertier (via)
My (limited) experience is that folks tend to focus on moving the data between versions, and don't always think about the other ramifications involved in upgrading to a new major version of MySQL.

MySQL 3.23, 4.0, 4.1 Reference Manual :: 2.11.1 Upgrading from MySQL 4.0 to 4.1

by mbertier (via)
In general, you should do the following when upgrading from MySQL 4.0 to 4.1:

PUBLIC TAGS related to tag migration

.net +   clevermarks +   controls +   cvs +   dev +   forms +   gratuit +   groupe:clever-age +   html5 +   microsoft +   module +   écran +   étape +   progressif +   svn +   vb +   vb.net +   vb6 +   visual_basic +   web +  

Active users

mfaure
last mark : 03/04/2017 11:33

jmfontaine
last mark : 08/06/2008 17:52

webs
last mark : 20/07/2007 00:08

martinsam
last mark : 11/07/2007 13:40

kasi77
last mark : 07/05/2007 08:13

mbertier
last mark : 02/10/2006 08:46