<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style>

   zlinux: joined #tikiwiki
   zlinux_: joined #tikiwiki
   zlinux: joined #tikiwiki
   <br> joined #tikiwiki
   zlinux_: joined #tikiwiki
   Tiki|bot: Recent Bug:  - http://dev.tiki.org/item6447
   zlinux: joined #tikiwiki
   amette_: joined #tikiwiki
   tibo: joined #tikiwiki
   <br> hi everyone
   <br> somebody can help me ?
   <br> with tracker
   Jyhem_: joined #tikiwiki
   robertokir: joined #tikiwiki
   redflo: joined #tikiwiki
   RadoS: Moin, how can I find out which mysql type I've selected at install time?
   amette_: RadoS : https://dev.mysql.com/doc/refman/5.7/en/show-create-table.html will tell you the engine used to create the table
   RadoS: amette_, thanks, but is the choice myISAM vs. innoDB relevant only there, or does tiki/php save it somewhere, too, so to know which features are available and which not?
   <br> relevant =&gt; stored
   <br> I installed an original tiki in innoDB, now for testing and trying out I chose myISAM, but used a backup-dump from the original install with innoDB.
   <br> Also, in the dump I see tiki_pages is innoDB, but other tables are not... so that selection just matter for that table?
   amette_: left #tikiwiki
   <br> joined #tikiwiki
   chibaguy: joined #tikiwiki
   <br> polom
   amette_: left #tikiwiki
   <br> joined #tikiwiki
   amette__: <u>RadoS</u>: it's only ever relevant at table creation time. One can create databases with mixed engine tables, no problem. Might it be that you used a dump from a Tiki created with InnoDB and then ran the upgrade with MyISAM, so that the new tables were created with MyISM?
   <br> afaik Tiki doesn't store the choice anywhere, it's just the selection in the installer to choose with which "Engine=" option the create table statements will be generated. (Haven't looked at that code for a long time any more.)
   Jyhem_laptop: joined #tikiwiki
   zlinux: joined #tikiwiki
   RadoS: Ok, that is/ would be good, so I don't have to correct it afterwards.
   <br> The Engine selection is stored in the dump, so it's restored 1:1.
   amette_: exactly. You can also just edit the dump with an editor and change the engines to make them all the same.
   RadoS: But... apparently some feature depend on this, how does the code know what works &amp; what not?
   amette_: Which is not needed as you mentioned in your first sentence, but if you want to tune for a special case, it is good.
   RadoS: Like full-text search.
   amette_: pretty good question, I got no idea
   -: RadoS nods.
   amette_: <u>Also</u>: I think full-text search is available in InnoDB nowadays, no!?
   RadoS: I though ISAM was lacking it while innoDB had it all along?! :)
   <br> +t
   amette_: oh, ok, hehe, not sure now *g*
   RadoS: I think that was why I chose innoDB back then, because people were complaining search failed in the old mediawiki.
   amette_: hmmmm.....
   <br> Since MySQL 5.6 both support full-text search, didn't find yet which one didn't before, but I'm rather sure it was InnoDB...
   <br> Anyway... Reason for InnoDb has for years been: ACID-compliance. Which is not that critical in a web application like Tiki. Downside was no full-text search and maybe performance. Both are fixed nowadays afaik, so you should try InnoDB for all your tables, if you can.
   RadoS: I trust the installer to do the "right thing".
   <br> I chose innoDB when I installed 1st time, so I stick with it.
   amette_: Sounds good! *thumbsup*
   RadoS: ACID _might_ have been a reason, but I don't remember now anymore. ;)
   amette_: left #tikiwiki
   <br> joined #tikiwiki
   <br> left #tikiwiki
   <br> joined #tikiwiki
   arildb: joined #tikiwiki
   Tiki|bot: Recent Bug:  - http://dev.tiki.org/item6448
   amette_: left #tikiwiki
   <br> joined #tikiwiki
   fabricius: joined #tikiwiki
   Telesight: joined #tikiwiki
   Jyhem_laptop: joined #tikiwiki
   fabricius: joined #tikiwiki