Some database column's name change after upgrade

[Sicoval31]

Code of Conduct

• I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues

GLPI Version

10.0.17

Plugin version

1.21.21

Bug description

Hi, since few release, one of the column name in the database change at each new release.
the name is plugin_fields_directionfielddropdowns_id_d1371005885 instead of plugin_fields_directionfielddropdowns_id for other fields from the glpi_plugin_fields_directionfielddropdowns table
And so, the _d1371005885 change every upgrade.
The probleme is i have many SQL request use this fields .... SQL in error after update or rebuild group fields.

No other fields impacted.

Thanks

---

French answer prefered :)

[stonebuzz]

Hello,

I couldn’t find anything in the code that would explain the addition of a numeric suffix to the column name. Also, I haven’t been able to reproduce this behavior locally, which makes investigation difficult.

Given the limitations of community support and the fact that I can’t perform any remote access, I suggest either trying to debug the issue locally to identify the root cause, or considering a professional subscription, which would allow us to take a deeper look.

Thanks for your understanding.

Best regards

[wimaerts]

I have the same issue. It is one of the reasons i dont upgrade our GLPI that often. Came here looking for this issue.

[stonebuzz]

Without additional information, it will be challenging to determine the root cause of the issue. We need as much detail as possible, including the impacted fields and their types, their configurations, the configuration of the associated container, SQL EXPLAIN plans for the tables and containers involved, and any other relevant details.

[wimaerts]

This is what i'm seeing in the table glpi_plugin_fields_fields after doing an upgrade of the plugin in our dev environment. In the past some fields got "two" added to the name after upgrading, thats not happening this time, but as u can see in the screenshots some fields get a different name after the upgrade.

[stonebuzz]

what was the original version of the plugin (before it was updated)

[Sicoval31]

I update each new version and had this problem since few version only (not remember when exactly). Add screenshot in the first post
I had pro support (reset due to new membership politic)

[wimaerts]

This time i came from 1.21.0 , but i've had this issue in the past in older versions too

[stonebuzz]

I update each new version and had this problem since few version only (not remember when exactly). Add screenshot in the first post I had pro support (reset due to new membership politic)

can you past here sql resultat for

EXPLAIN glpi_plugins_fields_fields;

[stonebuzz]

fields got "two" added

if two fields (or more) have the same nameas another, plugin add digit after (one, two, thee etc ..)

[Sicoval31]

[stonebuzz]

can you now past here sql resultat for

select * from glpi_plugins_fields_fields;

[Sicoval31]

plugin_fields_fields.csv
A csv file, (47 rows)

[stonebuzz]

In my opinion, line 88 was likely replaced by line 5, as both are of the same type: 'dropdown'.
However, line 88 still uses the old naming convention, for reasons that remain unclear.
We should normalize the database structure by renaming columns like *_d1371005885 to plugin_fields_directionfielddropdowns_id.
After that, line 88 can be safely removed.
Of course, this change should first be tested in a pre-production environment.

[Sicoval31]

This field is use in many container. Line 5,20,33,88 link to the "same" data generate first by the field at line 5 (intitulés GLPI ; champ directions)
I can't delete the line 88, i need this field int the container_id 19

I think i'll no more update the plugin and wait for GLPI11