You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-user@jakarta.apache.org by Kiyoko Takanabe <ta...@i-d-i-m.com> on 2001/09/04 09:08:05 UTC
ERROR 1073: create database specify "type=InnoDB"!
Hi,
I tried create database specify "type=InnoDB".
with the following script:
>create table objects(uri blob not null, primary key uriIndex (uri(255)),
classname blob) type=InnoDB;
I'm getting the following error
ERROR 1073: BLOB column 'uri' can't be used in key specification with the used table type
Is it supported with slide? If yes, please let me know how?
Any help is welcome.
----- Original Message -----
From: "Dirk Verbeeck" <di...@pandora.be>
To: <sl...@jakarta.apache.org>
Sent: Saturday, September 01, 2001 8:31 AM
Subject: Re: What should i use mysql table type to do transactions?
Kiyoko Takanabe wrote:
> Hello All,
>
> We tryied to use mysql v3.23+ via JDBC.
> I have some question.
>
> Prior to version 3.23, MySQL had no support for transactions, so Slide's standard JDBC store cannot populate the namespace
properly.
>
> Slide use mysql Table type 'myisam' by default,
> but myisam has no support for transactions.
>
> As a workaround, should i use innoDB type?
>
> ___________________________________________
> iDimension Inc.
> Kiyoko Takanabe
I don't use a mysql database but InnoDB seems the best table type.
Please report back if this type works for you.
Dirk
Re: ERROR 1073: create database specify "type=InnoDB"!
Posted by Kiyoko Takanabe <ta...@i-d-i-m.com>.
Hi,
Sorry, I think my idia is wrong.
I couldn't solve the problems.
There is no indexing the BLOB columns with InnoDB tables in MySQL yet.
I'll ask the mySQL mailing list for a solution and send you the results.
regards.
Kiyoko
----- Original Message -----
From: "Kiyoko Takanabe" <ta...@i-d-i-m.com>
To: <sl...@jakarta.apache.org>
Sent: Wednesday, September 05, 2001 5:26 PM
Subject: Re: ERROR 1073: create database specify "type=InnoDB"!
> Hi, Dirk
>
> Thank you for your advice, my problem is cleared.
>
> >create table objects(uri blob not null, unique index(uri(255)), classname blob);
>
> Regards.
>
> ___________________________________________
> Kiyoko Takanabe
>
> ----- Original Message -----
> From: "Dirk Verbeeck" <di...@pandora.be>
> To: <sl...@jakarta.apache.org>
> Sent: Wednesday, September 05, 2001 6:14 AM
> Subject: Re: ERROR 1073: create database specify "type=InnoDB"!
>
>
> > Kiyoko Takanabe wrote:
> >
> > > Hi,
> > >
> > > I tried create database specify "type=InnoDB".
> > > with the following script:
> > >
> > > >create table objects(uri blob not null, primary key uriIndex (uri(255)),
> > > classname blob) type=InnoDB;
> > >
> > > I'm getting the following error
> > >
> > > ERROR 1073: BLOB column 'uri' can't be used in key specification with the used table type
> > >
> > > Is it supported with slide? If yes, please let me know how?
> > > Any help is welcome.
> >
> > This is what I found in the mySQL docs:
> > * Only the MyISAM table type supports indexing on BLOB and TEXT columns. When putting an index on a BLOB or TEXT column you MUST
> > always specify the length of the index:
> > CREATE TABLE test (blob_col BLOB, index(blob_col(10)));
> >
> > You could change the uri to varchar but...
> > * Values in VARCHAR columns are variable-length strings. You can declare a VARCHAR column to be any length between 1 and 255,
> > just as for CHAR columns.
> >
> > That's not very good, you can choose
> > - transactions but uri limited to 255 chars
> > - no limit but also no transactions
> >
> > If you can live with no transactions use the slidestore.mysql.MySQLDescriptorsStore that was created for older version of mySQL.
> >
> > Maybe ask the mySQL mailing list for a solution.
> >
> >
> > Dirk
> >
> >
>
>
RE: Problem when cancelling during upload
Posted by Jacob Lund <ja...@qualiware.com>.
Hi Dirk!
Yes, I am using cloudscape for both content and structure. I have tried
both cloudscape 36 and 40. I run the database embedded and
client-server. This happens when I upload a new resource and overwrite.
What I don't understand is the "ResultSet not open". I have been
investigating a bit and it is only the when I access the directory where
the files has been uploaded.
Unfortunately the problem is not consistent - it is a periodic problem.
I use win2K sp2 and IE 5.5sp2/6.0. As webdav client I use windows
explorer.
If you have a cloudscape, then I could send you a copy og the database.
I think the data is corrupted somehow.
Jacob Lund
QualiWare ApS
-----Original Message-----
From: Dirk Verbeeck [mailto:dirk.verbeeck@pandora.be]
Sent: 9. september 2001 22:38
To: slide-user@jakarta.apache.org
Subject: Re: Problem when cancelling during upload
Jacob Lund wrote:
> Hi,
>
> If I upload a file to the slide server using Windows Explorer and the
> press cancel during the upload, then the server does not perform a
> proper rollback.
>
> If I use cloudscape database - then 5 out of 6 time the upload
> continues and 1 out of 6 I get the following error:
>
> 05 Sep 2001 13:35:26 - slidestore.reference.JDBCDescriptorsStore -
> ERROR
> - SQL E
> xception: ResultSet not open, operation next not permitted. Verify
that
> autocomm
> it is OFF.
> ERROR XCL16: ResultSet not open, operation next not permitted. Verify
> that autoc
> ommit is OFF.
> at c8e.p.b.newException(Unknown Source)
> at c8e.bg.ay.getNextRow(Unknown Source)
> at c8e.z.l.movePosition(Unknown Source)
> at c8e.z.l.movePosition(Unknown Source)
> at c8e.z.l.next(Unknown Source)
> at
> slidestore.reference.JDBCDescriptorsStore.retrieveRevisionDescriptors
> (JDBCDescriptorsStore.java:1284)
> at
> org.apache.slide.store.StandardStore.retrieveRevisionDescriptors(Stan
> dardStore.java:480)
>
> If I do this using hsql the upload cancels and the filename appears as
> a directory. MS SQL using the i-net driver also uploads the file after
> cancel has been pressed.
>
> I am using the slide version 1.0.14
>
> Jacob
Some questions:
Are you using cloudscape for both structure and content ? Embeddend or
client-server ? Are you creating a new resource on the server or
overwriting an old one?
Dirk
Re: Problem when cancelling during upload
Posted by Dirk Verbeeck <di...@pandora.be>.
Jacob Lund wrote:
> Hi,
>
> If I upload a file to the slide server using Windows Explorer and the
> press cancel during the upload, then the server does not perform a
> proper rollback.
>
> If I use cloudscape database - then 5 out of 6 time the upload continues
> and 1 out of 6 I get the following error:
>
> 05 Sep 2001 13:35:26 - slidestore.reference.JDBCDescriptorsStore - ERROR
> - SQL E
> xception: ResultSet not open, operation next not permitted. Verify that
> autocomm
> it is OFF.
> ERROR XCL16: ResultSet not open, operation next not permitted. Verify
> that autoc
> ommit is OFF.
> at c8e.p.b.newException(Unknown Source)
> at c8e.bg.ay.getNextRow(Unknown Source)
> at c8e.z.l.movePosition(Unknown Source)
> at c8e.z.l.movePosition(Unknown Source)
> at c8e.z.l.next(Unknown Source)
> at
> slidestore.reference.JDBCDescriptorsStore.retrieveRevisionDescriptors
> (JDBCDescriptorsStore.java:1284)
> at
> org.apache.slide.store.StandardStore.retrieveRevisionDescriptors(Stan
> dardStore.java:480)
>
> If I do this using hsql the upload cancels and the filename appears as a
> directory. MS SQL using the i-net driver also uploads the file after
> cancel has been pressed.
>
> I am using the slide version 1.0.14
>
> Jacob
Some questions:
Are you using cloudscape for both structure and content ?
Embeddend or client-server ?
Are you creating a new resource on the server or overwriting an old one?
Dirk
Problem when cancelling during upload
Posted by Jacob Lund <ja...@qualiware.com>.
Hi,
If I upload a file to the slide server using Windows Explorer and the
press cancel during the upload, then the server does not perform a
proper rollback.
If I use cloudscape database - then 5 out of 6 time the upload continues
and 1 out of 6 I get the following error:
05 Sep 2001 13:35:26 - slidestore.reference.JDBCDescriptorsStore - ERROR
- SQL E
xception: ResultSet not open, operation next not permitted. Verify that
autocomm
it is OFF.
ERROR XCL16: ResultSet not open, operation next not permitted. Verify
that autoc
ommit is OFF.
at c8e.p.b.newException(Unknown Source)
at c8e.bg.ay.getNextRow(Unknown Source)
at c8e.z.l.movePosition(Unknown Source)
at c8e.z.l.movePosition(Unknown Source)
at c8e.z.l.next(Unknown Source)
at
slidestore.reference.JDBCDescriptorsStore.retrieveRevisionDescriptors
(JDBCDescriptorsStore.java:1284)
at
org.apache.slide.store.StandardStore.retrieveRevisionDescriptors(Stan
dardStore.java:480)
If I do this using hsql the upload cancels and the filename appears as a
directory. MS SQL using the i-net driver also uploads the file after
cancel has been pressed.
I am using the slide version 1.0.14
Jacob
Re: ERROR 1073: create database specify "type=InnoDB"!
Posted by Kiyoko Takanabe <ta...@i-d-i-m.com>.
Hi, Dirk
Thank you for your advice, my problem is cleared.
>create table objects(uri blob not null, unique index(uri(255)), classname blob);
Regards.
___________________________________________
Kiyoko Takanabe
----- Original Message -----
From: "Dirk Verbeeck" <di...@pandora.be>
To: <sl...@jakarta.apache.org>
Sent: Wednesday, September 05, 2001 6:14 AM
Subject: Re: ERROR 1073: create database specify "type=InnoDB"!
> Kiyoko Takanabe wrote:
>
> > Hi,
> >
> > I tried create database specify "type=InnoDB".
> > with the following script:
> >
> > >create table objects(uri blob not null, primary key uriIndex (uri(255)),
> > classname blob) type=InnoDB;
> >
> > I'm getting the following error
> >
> > ERROR 1073: BLOB column 'uri' can't be used in key specification with the used table type
> >
> > Is it supported with slide? If yes, please let me know how?
> > Any help is welcome.
>
> This is what I found in the mySQL docs:
> * Only the MyISAM table type supports indexing on BLOB and TEXT columns. When putting an index on a BLOB or TEXT column you MUST
> always specify the length of the index:
> CREATE TABLE test (blob_col BLOB, index(blob_col(10)));
>
> You could change the uri to varchar but...
> * Values in VARCHAR columns are variable-length strings. You can declare a VARCHAR column to be any length between 1 and 255,
> just as for CHAR columns.
>
> That's not very good, you can choose
> - transactions but uri limited to 255 chars
> - no limit but also no transactions
>
> If you can live with no transactions use the slidestore.mysql.MySQLDescriptorsStore that was created for older version of mySQL.
>
> Maybe ask the mySQL mailing list for a solution.
>
>
> Dirk
>
>
Re: ERROR 1073: create database specify "type=InnoDB"!
Posted by Dirk Verbeeck <di...@pandora.be>.
Kiyoko Takanabe wrote:
> Hi,
>
> I tried create database specify "type=InnoDB".
> with the following script:
>
> >create table objects(uri blob not null, primary key uriIndex (uri(255)),
> classname blob) type=InnoDB;
>
> I'm getting the following error
>
> ERROR 1073: BLOB column 'uri' can't be used in key specification with the used table type
>
> Is it supported with slide? If yes, please let me know how?
> Any help is welcome.
This is what I found in the mySQL docs:
* Only the MyISAM table type supports indexing on BLOB and TEXT columns. When putting an index on a BLOB or TEXT column you MUST
always specify the length of the index:
CREATE TABLE test (blob_col BLOB, index(blob_col(10)));
You could change the uri to varchar but...
* Values in VARCHAR columns are variable-length strings. You can declare a VARCHAR column to be any length between 1 and 255,
just as for CHAR columns.
That's not very good, you can choose
- transactions but uri limited to 255 chars
- no limit but also no transactions
If you can live with no transactions use the slidestore.mysql.MySQLDescriptorsStore that was created for older version of mySQL.
Maybe ask the mySQL mailing list for a solution.
Dirk