Troubleshooting

Record title not as expected

If you are seeing your record titles displaying unexpected data, check the title fields are defined correctly in the table admin page.

If the record titles are displaying correctly on their own record details pages but not when returned on a related table summary, then you should check that the foreign key relationship is defined specifically for that relationship.

Example

There is a table, "status", that is defined as follows:

+--------+--------------+------+-----+---------+----------------+
| Field  | Type         | Null | Key | Default | Extra          |
+--------+--------------+------+-----+---------+----------------+
| id     | int unsigned | NO   | PRI | NULL    | auto_increment |
| name   | varchar(30)  | YES  |     | NULL    |                |
| closed | tinyint(1)   | YES  |     | 0       |                |
+--------+--------------+------+-----+---------+----------------+

The `name` field is defined as a "main" title field and the table contains the following rows:

+----+------------------+--------+
| id | name             | closed |
+----+------------------+--------+
|  1 | New              |      0 |
|  2 | In progress      |      0 |
|  3 | Testing          |      0 |
|  4 | Client to revert |      0 |
|  5 | Resolved         |      1 |
|  6 | Closed           |      1 |
+----+------------------+--------+

This is referenced from the `status` field on another table, `call`, which is defined as follows:

+--------------+--------------+------+-----+---------+-------------------+
| Field        | Type         | Null | Key | Default | Extra             |
+--------------+--------------+------+-----+---------+-------------------+
| call_ref     | int unsigned | NO   | PRI | NULL    | auto_increment    |
| request_type | int unsigned | YES  | MUL | NULL    |                   |
| priority     | int unsigned | YES  | MUL | NULL    |                   |
| summary      | varchar(255) | YES  |     | NULL    |                   |
| description  | text         | YES  |     | NULL    |                   |
| status       | int unsigned | YES  | MUL | NULL    |                   |
| raised_by    | int unsigned | YES  | MUL | NULL    |                   |
| assigned_to  | int unsigned | YES  | MUL | NULL    |                   |
| created_at   | timestamp    | YES  |     | now()   | DEFAULT_GENERATED |
+--------------+--------------+------+-----+---------+-------------------+

However, despite the `name` field being defined as a "main" title field, the call summary is displayed like this:

In this case, the issue is that there is no foreign key relationship defined specifically for the `status` field on the `call` table. To fix this, you would need to run the following SQL command to create a foreign key relationship between the `status` field on the `call` table and the `id` field on the `status` table:

ALTER TABLE call
ADD FOREIGN KEY (status) REFERENCES status(id);

After running this command, the call summary will display as expected:

Connection problems

If Redbrix cannot connect to your database, work through the following checks:

• Host and port: Confirm the hostname or IP address is correct and that the server is listening on the port you entered (MySQL defaults to 3306).
• Remote access: Your MySQL server must accept remote connections. Also, if applicable, check that your firewall allows inbound connections from address 13.134.60.54 on the database port (usually 3306 for MySQL).
• User permissions: The database user must be allowed to connect from remote hosts. A user defined as 'user'@'localhost' will be rejected — you may need a 'user'@'%' (or specific host) grant.
• Credentials: Double-check the username, password, and database name. These are case-sensitive on most servers.

If you are still unable to connect, contact us and we will do our best to help.