Support

You can ignore this. This is a Joomla! bug.

Let me explain. You'll have a good laugh.

Let's say that a database table at version X has a field with a specific definition, e.g. TINYINT(1).

Let's say that the same field on the same database table at a later version Y changes its definition, e.g. to TINYINT(2).

Both changes exist in the update SQL files of the component. Each SQL update file has a version, too, so Joomla! knows which one is the latest version. Keep that in mind…

What you would reasonably expect Joomla to do is reconcile these two updates by only taking the latest into account, since the natural progression of updates would result in that being the normative, latest definition of that field as it should be in the database.

What Joomla actually does is take into account both update files, expecting the same field to have two different definitions at the same time. Obviously this can never be the case, hence the nonsensical error you can never dismiss.

I haven't found a good solution. Going back to change or remove existing SQL update files makes it impossible to upgrade from older versions of ATS to new ones, since that closes the previously tested upgrade path. Not doing that makes Joomla trip and report an error which doesn't exist. Not using Joomla for SQL updates –which we were doing for a decade and worked perfectly well– makes certain Joomla maintainers of dubious capability and provable malice accuse us for unrelated problems we report. So, my choice was to let Joomla bug out since a. it's ultimately Joomla's bug to fix and b. while annoying, it doesn't cause any actual problem.