Stijn - indeed, same problem here. Of course, there appear to be no real solid test matrices online for releases, so it probably isn't you - it is probably just untested. (I know one of the major developers uses only Oracle .. probably leaves MySQL as a lower priority.)

I think I attached a mysqldump file on this list at some point to help others, because of this problem (I pbtained it from an old schema I had loaded from another version) ... i dont know if you have the archives but look there for it.

Cheers!
Jeremy

Stijn de Witt wrote:

Looking at the SQL in turbine-mysql.sql, it seems to be for the wrong
database type. Maybe a mixup? It looks like this (just the first two
tables):

----------------------------------------------------------------------------
-
-- TURBINE_PERMISSION
----------------------------------------------------------------------------
-
CREATE TABLE TURBINE_PERMISSION
(
   PERMISSION_ID integer NOT NULL IDENTITY,
   PERMISSION_NAME VARCHAR (99) NOT NULL,
   OBJECTDATA BINARY,
   PRIMARY KEY(PERMISSION_ID),
   UNIQUE (PERMISSION_NAME)
);

----------------------------------------------------------------------------
-
-- TURBINE_ROLE
----------------------------------------------------------------------------
-
CREATE TABLE TURBINE_ROLE
(
   ROLE_ID integer NOT NULL IDENTITY,
   ROLE_NAME VARCHAR (99) NOT NULL,
   OBJECTDATA BINARY,
   PRIMARY KEY(ROLE_ID),
   UNIQUE (ROLE_NAME)
);


It used to look like this:

# -----------------------------------------------------------------------
# TURBINE_PERMISSION
# -----------------------------------------------------------------------
drop table if exists TURBINE_PERMISSION;

CREATE TABLE TURBINE_PERMISSION
(
   PERMISSION_ID INTEGER NOT NULL AUTO_INCREMENT,
   PERMISSION_NAME VARCHAR (99) NOT NULL,
   OBJECTDATA BLOB,
   PRIMARY KEY(PERMISSION_ID),
   UNIQUE (PERMISSION_NAME)
);

# -----------------------------------------------------------------------
# TURBINE_ROLE
# -----------------------------------------------------------------------
drop table if exists TURBINE_ROLE;

CREATE TABLE TURBINE_ROLE
(
   ROLE_ID INTEGER NOT NULL AUTO_INCREMENT,
   ROLE_NAME VARCHAR (99) NOT NULL,
   OBJECTDATA BLOB,
   PRIMARY KEY(ROLE_ID),
   UNIQUE (ROLE_NAME)
);

Maybe I should try to run the old script?
-Stijn


----- Original Message ----- From: "Stijn de Witt" <[EMAIL PROTECTED]>
To: "Jetspeed Users List" <[EMAIL PROTECTED]>
Sent: Saturday, June 05, 2004 12:59 PM
Subject: How to change from hsqldb to mysql?





Hi,

I had previously changed the jetspeed user database from hsqldb to mysql.
However on jetspeed 1.5 I get errors running the turbine-mysql.sql script:

Anybody know what they are (and how to fix them)?
-Stijn

-----
mysql> use codamo;
Database changed
mysql> source



C:/bit/dev/project/bergland-portal/jetspeed/src/sql/external/turbine-mysql.s


ql
ERROR 1064: You have an error in your SQL syntax.  Check the manual that
corresponds to your MySQL server version for the right syntax to use near
'IDENTITY,
   PERMISSION_NAME VARCHAR (99) NOT NULL,
   OBJE
ERROR 1064: You have an error in your SQL syntax.  Check the manual that
corresponds to your MySQL server version for the right syntax to use near
'IDENTITY,
   ROLE_NAME VARCHAR (99) NOT NULL,
   OBJECTDATA
ERROR 1064: You have an error in your SQL syntax.  Check the manual that
corresponds to your MySQL server version for the right syntax to use near
'IDENTITY,
   GROUP_NAME VARCHAR (99) NOT NULL,
   OBJECTDAT
Query OK, 0 rows affected (0.02 sec)

Query OK, 0 rows affected (0.00 sec)
Records: 0  Duplicates: 0  Warnings: 0

ERROR 1064: You have an error in your SQL syntax.  Check the manual that
corresponds to your MySQL server version for the right syntax to use near
'IDENTITY,
   LOGIN_NAME VARCHAR (32) NOT NULL,
   PASSWORD_
Query OK, 0 rows affected (0.00 sec)

Query OK, 0 rows affected (0.00 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.02 sec)

ERROR 1064: You have an error in your SQL syntax.  Check the manual that
corresponds to your MySQL server version for the right syntax to use near
'IDENTITY,
   COFFEE_NAME VARCHAR (50),
   SUPPLIER_ID integ
Query OK, 0 rows affected (0.00 sec)
-----


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to