Upgrade from 1.5.3c to 15.4

bogolubow
Topic Author
Offline
New Member

13 years 6 months ago #15627 by bogolubow

Upgrade from 1.5.3c to 15.4 was created by bogolubow

When i try upgrade i see that message:

Code:

JInstaller::install: Błąd SQL DB function failed with error number 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 'TYPE=MyISAM CHARACTER SET `utf8` COLLATE `utf8_general_ci`' at line 8 SQL=CREATE TABLE IF NOT EXISTS `jos_flexicontent_cats_item_relations` ( `catid` int(11) NOT NULL default '0', `itemid` int(11) NOT NULL default '0', `ordering` int(11) NOT NULL default '0', PRIMARY KEY (`catid`,`itemid`), KEY `catid` (`catid`), KEY `itemid` (`itemid`) ) TYPE=MyISAM CHARACTER SET `utf8` COLLATE `utf8_general_ci`;
SQL =
CREATE TABLE IF NOT EXISTS `jos_flexicontent_cats_item_relations` (
  `catid` int(11) NOT NULL default '0',
  `itemid` int(11) NOT NULL default '0',
  `ordering` int(11) NOT NULL default '0',
  PRIMARY KEY  (`catid`,`itemid`),
  KEY `catid` (`catid`),
  KEY `itemid` (`itemid`)
) TYPE=MyISAM CHARACTER SET `utf8` COLLATE `utf8_general_ci`;
Komponent Zainstaluj: Błąd SQL, brak lub niezrozumiały plik .sql DB function failed with error number 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 'TYPE=MyISAM CHARACTER SET `utf8` COLLATE `utf8_general_ci`' at line 8 SQL=CREATE TABLE IF NOT EXISTS `jos_flexicontent_cats_item_relations` ( `catid` int(11) NOT NULL default '0', `itemid` int(11) NOT NULL default '0', `ordering` int(11) NOT NULL default '0', PRIMARY KEY (`catid`,`itemid`), KEY `catid` (`catid`), KEY `itemid` (`itemid`) ) TYPE=MyISAM CHARACTER SET `utf8` COLLATE `utf8_general_ci`;
SQL =
CREATE TABLE IF NOT EXISTS `jos_flexicontent_cats_item_relations` (
  `catid` int(11) NOT NULL default '0',
  `itemid` int(11) NOT NULL default '0',
  `ordering` int(11) NOT NULL default '0',
  PRIMARY KEY  (`catid`,`itemid`),
  KEY `catid` (`catid`),
  KEY `itemid` (`itemid`)
) TYPE=MyISAM CHARACTER SET `utf8` COLLATE `utf8_general_ci`;

On Windows 7 with XAMPP... joomla 1.5.20

Someone help me?

Please Log in or Create an account to join the conversation.

micker
Offline
Administrator

13 years 6 months ago #15638 by micker

Replied by micker on topic Upgrade from 1.5.3c to 15.4

try to update with this
code.google.com/p/flexicontent/d ... z&can=2&q=
regards

FLEXIcontent is Free but involves a very big effort on our part.
Like the our support? (for a bug-free FC, despite being huge extension) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing reviews. Thanks![/size]

Please Log in or Create an account to join the conversation.

kenmcd
Offline
Moderator

13 years 6 months ago #15650 by kenmcd

Replied by kenmcd on topic Upgrade from 1.5.3c to 15.4

.
If you are using the latest version of XAMPP you may have a version of MySQL which no longer accepts TYPE=MyISAM.

In the FLEXIcontent SQL files replace all instances of TYPE=MyISAM
with ENGINE=MyISAM

And upgrade Joomla to 1.5.23.
V1.5.20 has security issues.
.

AllMedia4Joomla Project
Download AllMedia YouTube Feed Gallery module

Please Log in or Create an account to join the conversation.

rjo
Offline
New Member

13 years 4 months ago #17027 by rjo

Replied by rjo on topic Upgrade from 1.5.3c to 15.4

Thank you for this information. Unfortunately I found it too late.
I simply removed all occurences of type or engine = MyIsam and all references to fulltextsearch. That worked for the installation. I will see if that has any negative impact somewhere else.

It might be good to move this information to the page www.flexicontent.org/downloads/l ... rsion.html and the release notes.
Have a good day,

Please Log in or Create an account to join the conversation.

ggppdk
Offline
Administrator

13 years 4 months ago #17066 by ggppdk

Replied by ggppdk on topic Upgrade from 1.5.3c to 15.4

If you removed them then your tables were created with your MySQL database server Default (table) Engine, which for newer MySql Server is InnoDB and not MyISAM

BUT wait ... you upgraded, this means that your tables already existed so they remained as the were of type MyISAM ...

In general using InnoDB, will not have a negative effect. And InnoDB is better heavy loads since it uses row locking instead of table locking that MyISAM uses. But SELECTs can be slower than when using MyISAM.

Here is quote of more info:

For a load with more writes and reads, you will benefit from InnoDB. Because InnoDB provides row-locking rather than table-locking, your SELECTs can be concurrent, not just with each other but also with many INSERTs. However, unless you are intending to use SQL transactions, set the InnoDB commit flush to 2. This gives you back a lot of raw performance that you would otherwise lose when moving tables from MyISAM to InnoDB.

Regards

-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing with a 5-star...

Please Log in or Create an account to join the conversation.