I´ve detected that the mysql_schema.sql file doesn´t specify the engine of the tables while installing.
In some servers it gives an error message because of it, becase the default db engine doesn´t support the fulltext index
Error repared with this file for new installs.

The changes are:


Until the end of the file.
That´s all.

Note: Thanks for the zone moving


DO NOT DOWNLOAD THIS FILES IF VARIOUS BOARD DB USERS USED

Both files have to be uploaded to:

thanks

____________
? Zuker - EDDB - LPM - Sharefields

Zuker wrote: [View Post]

thanks

post traduced to spanish & posted in phpbb-es.com post

I can't remember why... but I have removed the TYPE=MyISAM for one particular reason...

I'll try to investigate why and eventually I'll let you know.

____________
Luca
SEARCH is the quickest way to get support.
Icy Phoenix ColorizeIt - CustomIcy - HON

MG or another with permmision for moving:

Rate if this other topic should be in this section.

I know what reason was that:

MyISAM is a non-transaccional db motor which uses table-level blocks.

So this means that it will get inter-block every time!!!
And many actions will be interrupted because another user was looking in that table.

--------------------------

The solution is puting the engine to InnoDB, which is a transaccional db motor which uses row-level blocks.
That means I´ll update the files with that & the index will be of kind of "INDEX"

EDITING:

IT gives errors when changing to InnoDB db motor if similar topics activated

ONLY DOWNLOAD THIS FILES IF YOU USE VARIOUS DB USERS ON THE BOARD DB

This others files use the TYPE=InnoDB

This will allow to users of une board page use it without stopping by the others users of the other page.

The similar topics has to be disabled.

Thanks novice programmer for all these hints.

____________
Luca
SEARCH is the quickest way to get support.
Icy Phoenix ColorizeIt - CustomIcy - HON

I suspect the tables here are a bit out of date now, but I thought I'd point out something. In the InnoDB script given above, all that has been done is to put TYPE=InnoDB at the end of each table. How does this actually solve the problem of a full text table index on MS servers?

Look for instance at:


hack_name and hack_file are still both text keys...  so nothing has been done to change the indexes that are used - where there are text indexes in the MYISAM tables, they remain text indexes in INNODB tables, surely this will cause the same "The used table type doesn't support FULLTEXT indexes" error...

I also don't think "multiple database users" is the reason MYISAM was dropped - since most MYSQL servers assign MYISAM by default! If you wanted to avoid MYISAM, your won't get round it by not declaring an alternative engine. (Perhaps that was what MG had in mind, or perhaps the fact that "TABLE" is deprecated, and was going to replace with "ENGINE"?).

Interesting note - MYSQL supports hyper-threading regardless of engine, and in fact in a number of cases MYISAM scales the better with multiple threads than InnoDB (See here), even if slower in some other cases (contrary to rumour that most people think MYISAM is the fastest of the disk engines, the truth is a lot more subtle - it depends largely on the sort of queries you're most likely to make).

Perhaps we should just use HEAP engines  

MyISAM engine is the unique engine that allows the FULLTEXT indexes.

InnoDB allows that two different users (from the mysql system, not from the net) can read the table at the same moment if one of them is writting data in the table, as MyISAM blocks the table from reading while it is being written, which do not happens with the InnoDB engine.


PS: Thanks for remember me that was out-of-date. I will start making the file for the lastest bulid right now (Thanks to god I am on holidays, no more things I have to study!)

Hail! I know what the differences between the two are.

What I mean is - the table fields are exactly the same in both your MyISAM and InnoDB schema files, the only difference is the type declaration. This means that any tables in the sql schema that have full text indexes will still remain, and so surely it should still generate errors on MS mysql servers

It do not give any error if you remove the "ADD FULLTEXT ..." lines at the script.

The only thing it affect is to the similar topics, which has to be deactivated.

novice programmer wrote: [View Post]

The changes are:

Code: [Download] [Hide] [Select]

Code: [Download] [Show]

Search

CREATE TABLE

Search

);

In-line remplace with:

)TYPE=MyIsam;

agrego eso al final del .sql?? o busco la parte ); y reemplazo por )TYPE=MyIsam; ??

todavia no pude instalar el icy    

Gushh wrote: [View Post]

novice programmer wrote: [View Post]

The changes are:

Code: [Download] [Hide] [Select]

Code: [Download] [Show]

Search

CREATE TABLE

Search

);

In-line remplace with:

)TYPE=MyIsam;

agrego eso al final del .sql?? o busco la parte ); y reemplazo por )TYPE=MyIsam; ??

todavia no pude instalar el icy    

tienes que reemplazar todos los ); por )TYPE=MyIsam; para las consultas de tipo "CREATE TABLE" (hay algunas que no son para hacer una tabla, sino para meter datos, que no necesitan este cambio.

por cierto, este foro usa como idioma primario el ingles, y pedimos a todos los usuarios que intenten usar este lenguaje para preguntar, ya que asi pueden conseguir soporte mas rapidamente. Tambien puedes escribir en ambos idiomas en tus mensajes. En caso de que tengas problemas al traducir, prueba a usar Google Translate. Ayuda mucho en esos casos.

En caso de que te sea muy dificil, hay una comunidad de soporte hispana de Icy Phoenix en Icy Phoenix España, reconocido por este sitio, y con varios de sus moderadores/administradores en nuestros esquipos de moderacion/administracion

__________________________


have to replace all ); for )TYPE=MyISAM; for all the queries of the "CREATE TABLE" kind (there are some that are not for creating a table, but for inserting data, which do not require this change.

BTW, this forum used as the primary language English, and we ask all users to try to use this language in their posts, so they can get answers and support quicker. You can also write in both languages on your messages. In case you have trouble translating, try using [url = http://translate.google.com] Google Translate [/ url]. It helps a lot in such cases.

Finally, in case you find posting in english very difficult, there is a Spanish support community for Icy Phoenix at Icy Phoenix Spain, recognized by this site, with several of their mods/admins also at the staff groups here.