...
MySQL Configuration
Table Type
There are a few options that should be set in MySQL, typically in either my.cnf (/etc/my.cnf on Unix) though there are other options such as startup flags, etc.
...
uPortal relies on database transactional support, which in MySQL
...
is dependent upon the underlying storage engine (per-table). The default (MyISAM) is not transaction safe. The most common transactional table type on MySQL is InnoDB.
Assuming you've got the needed statements for InnoDB tables in your my.cnf file, you can change already-created MyISAM tables to Innodb tables with an ALTER TABLE statement - see the documentation for the exact syntax. Or, you can drop all your tables and re-create them with "TYPE=InnoDB" on your CREATE TABLE statements. If you're not sure about using TST (Transaction Safe Tables), do some reading on the MySQL site (http://www.mysql.com) about some of the companies and organizations that are currently using them - for instance, Slashdot.org uses MySQL InnoDB tables to handle their more than 100,000 hits per week.
...
MySQL table names are case-sensitive depending on the filesystem of the server. e.g. insensitive on Windows & Mac HFS+, Case sensitive on Unix. To prevent issues when moving between platforms it is recommended that you set:
| Code Block | ||
|---|---|---|
|
...
| ||
[mysqld] lower_case_table_names=1 |
| Note |
|---|
...
If you |
...
have already created your database, and plan to change the http://dev.mysql.com/doc/refman/5.0/en/identifier-case-sensitivity.html |
Indexing
Another thing that is really needed to use MySQL with uPortal effectively is to index your tables - this way, uPortal queries will have to scan fewer records and set fewer locks - and this can speed up authentication into the portal tremendously. UP_USER, UP_USER_ATTS, ans UP_USER_PARM need to be indexed with a primary key - check out the documentation for your version of MySQL for the exact syntax.
...