Hi, > As it turned out it was not a bug, but a mis-configuration of > MySQL/BASE. The error happens when your database uses one charset, the > db.url setting in base.config uses a different charset and your data > contains a character outside the ASCII range. Check the data in the > Protocols table in BASE 1, and make sure the db.url uses the same > charset as the database.
Well, I got no errors during the migration, when I created the base2 and base2dynamic db with phpMyAdmin (latin1_swedish_ci collation), while I got some using the initdb script (utf-8). The next problem is: After a successful migration, I miss the pictures. :s I now wonder, what went wrong this time. Best regards Bernd ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ The BASE general discussion mailing list basedb-users@lists.sourceforge.net unsubscribe: send a mail with subject "unsubscribe" to [EMAIL PROTECTED]
