nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DataDeploy and MySQL

marcussteiner

Hi all,
does anybody know if we can deploy conent/metadata using DataDeploy to a MySQL database version 5.x. Officially only version 4.1.7 is supported but we only need to deploy some metadata into the database. I wonder if there is a way of doing so.

cheers
hollis

Find more posts tagged with

Comments

Migrateduser

I've been successful with Mysql 4.0.23 but that's not your question, I realize Smiley Happy

Have you downloaded Connector/J (http://dev.mysql.com/downloads/connector/j/3.1.html) and tried doing this?

marcussteiner

well... thanks for the answer but. yes that's not the question. I checked the page and that's what I thought that we only need to provide the right driver. bu t I havent got the change to test this.

jed

well... thanks for the answer but. yes that's not the question. I checked the page and that's what I thought that we only need to provide the right driver. bu t I havent got the change to test this.

Any update on this at all? I am curious if it would work as well. Also, the manual states that only "US English" is supported. Does this mean no UTF-8 support? Or is this because mysql 4 has limited utf-8 support. (If I remember correctly, mysql 5 has better support for utf-8.)

Migrateduser

Perhaps I'm being naive but since Mysql is such a low-impact service to install (meaning it's very straight-forward and carries little to no impact to other applications), I'm wondering why someone who needs to run DD with Mysql 5 just give it a try. I'm not on version 5 at the moment but I'm one of I'm sure many, many people who would be interested to know if this scenario works or not.

jed

I was able to deploy to mysql 5.x, but my data was not sent as UTF-8 Smiley Sad

Maybe have I something misconfigured on the DB side, but the fact that I cannot connect is good news.

Migrateduser

but the fact that I cannot connect is good news.

Do you mean that you can connect is good news? That's great to know that it works with Mysql 5, but are you running phpMyAdmin? If so, you can easily figure out what character set you're using by calling up "system variables". I don't know what the query is that displays this screen -- maybe "SHOW STATUS"?

Not sure.

jed

Buh! I meant to say the fact that I *can* connect is good news. It's been a looong week. Anyway:

My create statement:
CREATE DATABASE ddtest DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

CREATE TABLE `mysql_test` (
`object_id` varchar(255) NOT NULL default '',
`description` varchar(255) default '',
`title` varchar(255) default ''
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

I still have some vars set in latin1 land. Not sure how to get these all to utf8, or if these impact anything. If anyone has the correct my.cnf setting to flag everything as UTF8, please let me know.

mysql> show variables like "%character%";show variables like "%collation%";
+--------------------------+------------------------------------------+
| Variable_name | Value |
+--------------------------+------------------------------------------+
| character_set_client | latin1 |
| character_set_connection | latin1 |
| character_set_database | utf8 |
| character_set_results | latin1 |
| character_set_server | utf8 |
| character_set_system | utf8 |
| character_sets_dir | /home/local/mysql5/share/mysql/charsets/ |
+--------------------------+------------------------------------------+
7 rows in set (0.00 sec)

+----------------------+-------------------+
| Variable_name | Value |
+----------------------+-------------------+
| collation_connection | latin1_swedish_ci |
| collation_database | utf8_general_ci |
| collation_server | utf8_general_ci |
+----------------------+-------------------+

my.cnf
default-character-set=utf8
character-set-server = utf8
character-set-client=utf8
### these variations did not work
#character-set-connection=utf8
#character_set_connection=utf8
#character_set_results=utf8

Migrateduser

I'm sure you've seen this, but http://dev.mysql.com/doc/refman/5.0/en/charset.html. Thankfully, I haven't had to deal with character sets too much in the past few years but I tend to think that Mysql installs as latin1 by default.

jed

I'm sure you've seen this, but http://dev.mysql.com/doc/refman/5.0/en/charset.html. Thankfully, I haven't had to deal with character sets too much in the past few years but I tend to think that Mysql installs as latin1 by default.

Actually, my adhoc google searches did not pick up on that yet. Hopefully that will help my utf-8 woes.

Migrateduser

Oh, the MySQL Reference Manual is always on my list of bookmarks! It's such a helpful link... it's great when in a bind and in need of a quick reference.

jed

I have UTF-8 deployments working to a mysql 5.x server with the latest jdbc drivers. The key was getting the correct values in the my.cnf file.

1. setup mysql to use UTF-8 for all charset related activities

[mysqld]
character-set-server = utf8
init_connect='SET NAMES utf8'

2. verify all setting have taken affect

mysql> show variables like "%character%";show variables like "%collation%";
+--------------------------+------------------------------------------+
| Variable_name | Value |
+--------------------------+------------------------------------------+
| character_set_client | utf8 |
| character_set_connection | utf8 |
| character_set_database | utf8 |
| character_set_results | utf8 |
| character_set_server | utf8 |
| character_set_system | utf8 |
| character_sets_dir | /home/local/mysql5/share/mysql/charsets/ |
+--------------------------+------------------------------------------+
7 rows in set (0.00 sec)

+----------------------+-----------------+
| Variable_name | Value |
+----------------------+-----------------+
| collation_connection | utf8_general_ci |
| collation_database | utf8_general_ci |
| collation_server | utf8_general_ci |
+----------------------+-----------------+

3. Perform DD and verify utf-8 data

mysql> select * from mysql_test;
+-----------+-------------------------------------------+-----------------------------------------------------------+
| object_id | description | title |
+-----------+-------------------------------------------+-----------------------------------------------------------+
| 37163324 | 中国版 (China) - 香港版 (Hong Kong) | 한국 (Korea) - 台灣版 (Taiwan) - ישראל (Israel) |
+-----------+-------------------------------------------+-----------------------------------------------------------+
1 row in set (0.01 sec)

Bill Klish

I am having trouble now with ? showing up instead of the UTF-8 encoded ' recorded inside my DCR.

Mysql 5.0.15, DD 6.1, Solaris 2.9, Connector/J 3.1.11

What versions of things did you get this to work on?, and what is your locale on the server you are running the mysql client from? Toad for MySQL and the MySQL query browser are showing me the ?

jed

What versions of things did you get this to work on?, and what is your locale on the server you are running the mysql client from? Toad for MySQL and the MySQL query browser are showing me the ?

MySql Server: 5.0.16
Client: Solaris 9
Driver: mysql-connector 3.1.12
OD: 6.0.2.1.1

I have no idea what the default locale is set for the client. Once I set these values in mysql, everything started working:

[mysqld]
character-set-server = utf8
init_connect='SET NAMES utf8'

We also start some of our OD instaces with the following option in processod:
-Dfile.encoding=UTF-8

Example:
JAVA_OPTS="-server -Dfile.encoding=UTF-8 -Xsqnopause -XX:+PrintClassHistogram -XX:+PrintGCDetails -verbose:gc -Xss2m -Xms512m -Xmx1024m"

We are still on oracle, so this is about all I know about mysql. This was more of a POC effort.

Bill Klish

Thankfully the java opts weren't necessary. The server is not configured to support utf-8 (the character set server was listed as latin1, but everything else said utf8). I installed my own server and made sure everything was the same version, except I setup the database server to be utf-8. That did the trick.

Thanks for pointing me in the right direction. Now, I have to convince the ops people to change the server configuration. I just don't know what impacts that will have on all the existing schemas.

files.zip