Hey folks,
I'm a newbie.
My Name is Glenn Thompson (gat).
While trying to get the petclinic sample app running against MySQL 4.1.0
alpha, I ran into a few problems.
I figured I should share what I did to get it to work.:
1. The supplied initDB.txt script fails to work under 4.0.14 and 4.1.0.
2. I have attached a new script which will work for 4.0.14, 4.1.0 and
uses InnoDB for the non Sequence tables. It's the only table type that
supports foreign keys.
3. I had to change the name of the "types" table. "types" is a
reserved word under newer versions of MySQL. I renamed it "pet_types"
and the sequence table "pet_types_seq".
4. Because of item number three, AbstractJdbcClinic.java had to be
changed. See Attached. MysqlClinic didn't have to be changed as the
types sequence is not currently used by the app. At least as far as I
could see.
5. You may want to add a commented out "clinic" bean to the
applicationContext.xml that references MysqlClinic. I had it running
(and blowing up against) Mysql using the HsqlClinic business object. It
took me a little bit to figure out what I had done wrong. Thank god for
stack traces:-)
6. I was unable to get J/connector 3.1.x working. Not sure why. I
used 3.0.8
7. Under 4.1.0 the password handling has changed and is a little funky.
I had problems getting connections. Read the MySQL release notes.
Questions:
1. Has anyone tried to make the "setupDB task" create the DB when
"useMYSQL" is selected? I was just wondering if there was something
specific that kept it from being added to the task.
2. If I have other changes should I submit them as patches? If so,
which format do you folks prefer?
Thanks,
gat
PS Two thumbs up on J2EE D&D Rod!
|
