Attempt to create or modify table without primary key

Thanks for reporting Greg. A couple of questions:

1. Have you tried migrating to a regular hosting setup? If so, did you observe a similar error?
2. What is the specification of the managed database? You maybe able to use my other plugin, System Dashboard to get some key info.

Thanks again!

This is a DigitalOcean managed database. The error is caused because the MySQL system variable ‘sql_require_primary_key’ is set, as is the case with many managed databases. It’s possible to disable the setting, but not advisable. A better solution would be to add a sequential “entry_id” and use it as the table’s unique primary key.

Although the table contains non-sequential data, sequential IDs can be more efficient in terms of storage and indexing. Random or non-sequential identifiers might lead to index fragmentation, which can slow down query performance in some cases.

• This reply was modified 14 hours ago by Greg Mount.

@gregmount thank you for the detailed explanation. I’ve added an ‘id’ column and set that as the primary key in the failed_logins table in ASE v5.5.1.

Please keep the feedback coming. I love it when a root cause is identified and a fix/solution for it is clear, so I can go ahead and implement.