Feature Request: Select mysql table engine. #345

New Issue

Closed

opened 2018-09-23 19:38:39 +00:00 by peterpetrov · 4 comments

peterpetrov commented

2018-09-23 19:38:39 +00:00

(Migrated from github.com)

This feature request is to be able to select the engine for table creation when creating new Admin View. Currently it is only MyISAM. The benefit will be to create INNODB which will be better for some tables when the website is under heavy usage. The main difference is that MyISAM locks the whole table to insert or update a record. INNODB locks just the line in question. That can significantly decrease the load time for sites with a lot of content built with JCB.

Llewellyn commented

2018-09-25 20:08:42 +00:00

Okay in the admin view under the mySql tab there are three new select options, to tweak the table, give it a try and let me know it you run into any trouble.

This was a big changes, and I have tried my best to have it work in all shapes and sizes out of the box... hope that will be the case.

Okay in the admin view under the mySql tab there are three new select options, to tweak the table, give it a try and let me know it you run into any trouble. This was a big changes, and I have tried my best to have it work in all shapes and sizes out of the box... hope that will be the case.

peterpetrov commented

2018-09-26 05:35:25 +00:00

(Migrated from github.com)

It works perfectly. Thank you very much for that.

Llewellyn commented

2018-09-29 14:27:50 +00:00

Tell me @peterpetrov why would this error occur as @mwweb described in gh-348

JInstaller: :Install: Error SQL Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline.
Extension Update: SQL error processing query: DB function failed with error number 1118
Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline.
SQL =
ALTER TABLE #__componentbuilder_joomla_component ENGINE = InnoDB;

I think it is a local limitation, could I be wrong...

Tell me @peterpetrov why would this error occur as @mwweb described in gh-348 > > JInstaller: :Install: Error SQL Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline. > Extension Update: SQL error processing query: DB function failed with error number 1118 > Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline. > SQL = > ALTER TABLE #__componentbuilder_joomla_component ENGINE = InnoDB; I think it is a local limitation, could I be wrong...

peterpetrov commented

2018-09-29 14:51:15 +00:00

(Migrated from github.com)

That has to be local one. I will comment on the issue itself.