Hi Rahul, Thanks again for the tip. I am new to MySQL and thought it had something to do with the MySQL and not slide.
Regards Jim. PS Thanks also to the other people who replied. ----- Original Message ----- From: "Rahul" <[EMAIL PROTECTED]> To: "Slide Users Mailing List" <[EMAIL PROTECTED]> Sent: Saturday, November 16, 2002 2:13 AM Subject: Re: Domain.xml configuration for MySQL > Hi Jim, > > The MySQL error there has to do with MySQL server configuration. you can > refer to "GRANT PRIVILEGES ....." syntax to change privileges for > <user_name>@<host_name> (Please refer MySQL documentation). > > That should resolve that :-) > > Cheers, > > Rahul > > ----- Original Message ----- > From: "Jim Collins" <[EMAIL PROTECTED]> > To: "Slide Users Mailing List" <[EMAIL PROTECTED]> > Sent: Friday, November 15, 2002 7:36 PM > Subject: Re: Domain.xml configuration for MySQL > > > > Thanks Rahul, > > > > It is pretty much how I have got mine setup. I am getting the following > > error though when I startup Tomcat: > > > > 15 Nov 2002 00:32:36 - slidestore.reference.JDBCDescriptorsStore - INFO - > > Connecting to "jdbc:mysql://localhost:3306/myDB" as user "root" > > 15 Nov 2002 00:32:41 - slidestore.reference.JDBCDescriptorsStore - ERROR - > > Connecting to "jdbc:mysql://localhost:3306/myDB" as user "root" failed > > 15 Nov 2002 00:32:41 - slidestore.reference.JDBCDescriptorsStore - ERROR - > > java.sql.SQLException: Invalid authorization specification: Access denied > > for user: 'root@localhost' (Using password: YES) > > 15 Nov 2002 00:32:41 - org.apache.slide.common.Domain - WARNING - Service > > slidestore.reference.JDBCDescriptorsStore@a36b53 connection failed : > Invalid > > authorization specification: Access denied for user: 'root@localhost' > (Using > > password: YES) > > 15 Nov 2002 00:32:41 - org.apache.slide.common.Domain - WARNING - Service > is > > missing on root node > > 15 Nov 2002 00:32:41 - org.apache.slide.common.Namespace - ERROR - Unable > to > > read Namespace base configuration file : > > 15 Nov 2002 00:32:41 - org.apache.slide.common.Namespace - ERROR - > > org.apache.slide.common.ServiceMissingOnRootNodeException: Service is > > missing on root node > > org.apache.slide.common.ServiceMissingOnRootNodeException: Service is > > missing on root node > > > > I can access the database from mysql using the user name and password that > I > > set in Domain.xml but it does not seem to work from slide. > > > > Thanks for you help anyway. > > > > Jim. > > > > > > ----- Original Message ----- > > From: "Rahul" <[EMAIL PROTECTED]> > > To: "Slide Users Mailing List" <[EMAIL PROTECTED]> > > Sent: Friday, November 15, 2002 1:58 AM > > Subject: Re: Domain.xml configuration for MySQL > > > > > > > > > > Hi Jim, > > > > > > Below is a snippet of domain.xml for cofiguring slide with MySQL running > > on > > > localhost. > > > > > > Hope it helps !! > > > > > > Cheers :-) > > > > > > Rahul > > > > > > ************************************** > > > > > > <!-- ### JDBC Configuration ### > > > The following jdbc sample configuration uses the hsql Database > Engine > > > a relational database engine written in Java, for more info: > > > http://hsqldb.sourceforge.net/ > > > --> > > > <definition> > > > <store name="jdbc"> > > > <nodestore classname="slidestore.mysql.MySQLDescriptorsStore"> > > > <parameter name="driver">com.mysql.jdbc.Driver</parameter> > > > <parameter > > name="url">jdbc:mysql://localhost:3306/slide</parameter> > > > <parameter name="user">root</parameter> > > > <parameter name="password"></parameter> > > > </nodestore> > > > <securitystore> > > > <reference store="nodestore" /> > > > </securitystore> > > > <lockstore> > > > <reference store="nodestore" /> > > > </lockstore> > > > <revisiondescriptorsstore> > > > <reference store="nodestore" /> > > > </revisiondescriptorsstore> > > > <revisiondescriptorstore> > > > <reference store="nodestore" /> > > > </revisiondescriptorstore> > > > <contentstore classname="slidestore.mysql.MySQLContentStore"> > > > <parameter name="driver">com.mysql.jdbc.Driver</parameter> > > > <parameter > > name="url">jdbc:mysql://localhost:3306/slide</parameter> > > > <parameter name="user">root</parameter> > > > <parameter name="password">somepassword</parameter> > > > </contentstore> > > > </store> > > > <scope match="/" store="jdbc" /> > > > </definition> > > > > > > ****************************************** > > > > > > ----- Original Message ----- > > > From: "Jim Collins" <[EMAIL PROTECTED]> > > > To: "Slide Users Mailing List" <[EMAIL PROTECTED]> > > > Sent: Friday, November 15, 2002 12:59 PM > > > Subject: Domain.xml configuration for MySQL > > > > > > > > > > Hi, > > > > > > > > Does anyone have a configuration file for MySQL. > > > > > > > > Thanks > > > > > > > > Jim > > > > ----- Original Message ----- > > > > From: "Michael Wang" <[EMAIL PROTECTED]> > > > > To: <[EMAIL PROTECTED]> > > > > Sent: Thursday, November 14, 2002 11:22 PM > > > > Subject: URI limited to 255 in MySQL and DB2? > > > > > > > > > > > > > I found that URI column in OBJECTS and REVISIONS tables are limited > > > > > to 255 chars in MySQL and DB2, due to the primary key constraint. > > > > > > > > > > The purpose of this posting is to confirm this, and to seek opinions > > and > > > > > workaround. > > > > > > > > > > Thanks. > > > > > > > > > > (1) MySQL > > > > > > > > > > Copied from JDBC How To: > > > > > > > > > > " > > > > > create table objects(uri blob not null, primary key uriIndex > > (uri(255)), > > > > > classname blob); > > > > > " > > > > > > > > > > I believe PRIMARY KEY is used to enforce uniqueness as well as > > indexing. > > > > > If this is true, URI exceeds 255, and PRIMARY KEY is only done on > the > > > > > first 255 chars, then the uniqueness is not enforced. > > > > > > > > > > The key is limited to 255 on a single column in MySQL (both MyISAM > and > > > > > innoDB), having a larger URI column only create a hidden problem. It > > is > > > > > better to make the problem up front. For this reason, I would > suggest > > > > > changing above to > > > > > > > > > > " > > > > > create table objects(uri varchar(255) not null, primary key uriIndex > > > > (uri(255)), > > > > > classname blob); > > > > > " > > > > > > > > > > How do you think? And anyone has an idea to make URI beyond 255 in > > > MySQL? > > > > > > > > > > (2) DB2 > > > > > > > > > > The DB2 (version 7.1) has the same limitation on the length of > > > > > column with primary key, as shown below. > > > > > > > > > > " > > > > > db2 => create table obj(uri varchar(256) not null primary key, > > > > > db2 (cont.) => classname varchar(3200)); > > > > > > > > > > SQL20075 The index or index extension "SQL021114150625950" cannot > be > > > > created > > > > > or altered because the length of "URI" is more than 255 bytes. > > > > SQLSTATE=54008 > > > > > > > > > > db2 => create table obj(uri blob(256) not null primary key, > > > > > db2 (cont.) => classname varchar(3200)); > > > > > > > > > > SQL0350N LOB, DATALINK, or structured type column "URI" cannot be > > used > > > in > > > > an > > > > > index, a key, a unique constraint, a generated column, or a declared > > > > temporary > > > > > table. SQLSTATE=42962 > > > > > " > > > > > > > > > > Is there a way to go beyond 255 in DB2? > > > > > > > > > > Anyone has encountered the limitation in these two databases, and > > > > > has found a workaround? > > > > > > > > > > -- > > > > > Michael Wang > > > > > http://www.unixlabplus.com/ > > > > > > > > > > -- > > > > > To unsubscribe, e-mail: > > > > <mailto:[EMAIL PROTECTED]> > > > > > For additional commands, e-mail: > > > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > -- > > > > To unsubscribe, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > > For additional commands, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
