I upgraded to drupal 5.1 but I got these errors from amazontools. I've also attached my current db structure. What do I need to do to get my amazonitem table correct?
user warning: BLOB/TEXT column 'author' used in key specification
without a key length query: ALTER TABLE amazonitem CHANGE
Author author text in
/nfs/ank/home1/n/nebulonk/featuredrivendevelopment.com/includes/database.mysql.inc
on line 172.
user warning: Duplicate column name 'editorialreview' query: ALTER
TABLE amazonitem ADD editorialreview longtext in
/nfs/ank/home1/n/nebulonk/featuredrivendevelopment.com/includes/database.mysql.inc
on line 172.
user warning: Duplicate column name 'rating' query: ALTER TABLE
amazonnode ADD rating smallint in
/nfs/ank/home1/n/nebulonk/featuredrivendevelopment.com/includes/database.mysql.inc
on line 172.
user warning: BLOB/TEXT column 'title' used in key specification without
a key length query: ALTER TABLE amazonitem DROP INDEX Title,
CHANGE title title text, ADD INDEX title (title(100)) in
/nfs/ank/home1/n/nebulonk/featuredrivendevelopment.com/includes/database.mysql.inc
on line 172.
Update #1
ALTER TABLE {amazonitem} CHANGE ASIN asin VARCHAR(10)
ALTER TABLE {amazonitem} CHANGE DetailPageURL detailpageurl TEXT
ALTER TABLE {amazonitem} CHANGE SmallImageURL smallimageurl text
ALTER TABLE {amazonitem} CHANGE SmallImageHeight smallimageheight INT(10)
ALTER TABLE {amazonitem} CHANGE SmallImageWidth smallimagewidth INT(10)
ALTER TABLE {amazonitem} CHANGE MediumImageURL mediumimageurl text
ALTER TABLE {amazonitem} CHANGE MediumImageHeight mediumimageheight INT(10)
ALTER TABLE {amazonitem} CHANGE MediumImageWidth mediumimagewidth INT(10)
ALTER TABLE {amazonitem} CHANGE LargeImageURL largeimageurl text
ALTER TABLE {amazonitem} CHANGE LargeImageHeight largeimageheight INT(10)
ALTER TABLE {amazonitem} CHANGE LargeImageWidth largeimagewidth INT(10)
Failed: ALTER TABLE {amazonitem} CHANGE Author author text
ALTER TABLE {amazonitem} CHANGE Binding binding VARCHAR(100)
ALTER TABLE {amazonitem} CHANGE listAmount listamount INT(10)
ALTER TABLE {amazonitem} CHANGE listCurrencyCode listcurrencycode CHAR(3)
ALTER TABLE {amazonitem} CHANGE listFormattedPrice listformattedprice
VARCHAR(10)
ALTER TABLE {amazonitem} CHANGE Title title VARCHAR(100)
ALTER TABLE {amazonitem} CHANGE Amount amount INT(10)
ALTER TABLE {amazonitem} CHANGE CurrencyCode currencycode CHAR(3)
ALTER TABLE {amazonitem} CHANGE FormattedPrice formattedprice VARCHAR(10)
ALTER TABLE {amazonitem} CHANGE Availability availability VARCHAR(50)
Failed: ALTER TABLE {amazonitem} ADD editorialreview longtext
Failed: ALTER TABLE {amazonnode} ADD rating smallint
ALTER TABLE {amazonnode} CHANGE ASIN asin VARCHAR(10)
UPDATE {amazonnode} SET ntype='amazon_node' WHERE ntype='amazon-node'
UPDATE {node} SET type='amazon_node' WHERE type='amazon-node'
UPDATE {vocabulary_node_types} SET type='amazon_node' WHERE type='amazon-node'
Update #2
UPDATE {node} SET type = 'amazon_node' WHERE type = 'amazon-node'
UPDATE {amazonnode} SET ntype = 'amazon_node' WHERE ntype = 'amazon-node'
Update #3
Failed: ALTER TABLE {amazonitem} DROP INDEX Title, CHANGE title title text, ADD
INDEX title (title(100))
| Comment | File | Size | Author |
|---|---|---|---|
| Picture 2_6.png | 167.92 KB | jman |
Comments
Comment #1
Prometheus6 commentedamazon_item table:
on the title field, drop the Title index, change the title field's type to text and add a new index named title, using 100 characters.
Do the same with for the editorialreview field and the Author field. Technically the Author field should be all lowercase.
Curious...are you upgrading from 4.6?
Comment #2
jman commentedThanks. I did that but the trick was I also had to drop the author index first as it was a composite using title and that's what was stopping changing title. I changed title and author to text and editorialreview to longtext. I made author all lowercase.
I recreated title and author in the index like so
ADD INDEX author( author( 100 ) , title( 100 ) )
ADD INDEX title( title( 100 ) )
I assume that's ok? Everything seems to be working fine.
FYI - it was an upgrade from 4.7.
Comment #3
Prometheus6 commentedYeah, that's fine. There was a point at which I thought all the upgrades ran when you install the package.