Duplicate entries in Lexicon

I just noticed that my Revolution lexicon_entries table has *many* duplicate entries in the core namespace (about 5700 entries in all).


I don’t know if this happens in upgrade setup or in lexicon reload. Probably the latter, since I checked and it doesn’t effect any other tables that get values merged on upgrade setup.

Is it safe to just empty the lexicon_entries table and then "reload" in Lexicon Management?

That must be a problem with the reload, as I’m not seeing this anywhere. Though, just to be sure, duplicates would be same name, topic, and language; can you confirm you have duplicates in the same topics?

Quote from: BobRay at Oct 22, 2008, 05:42 PM

Is it safe to just empty the lexicon_entries table and then "reload" in Lexicon Management?

If that doesn’t work, just empty it again and run an upgrade. That should resolve it.

Quote from: BobRay at Oct 22, 2008, 05:42 PM

I just noticed that my Revolution lexicon_entries table has *many* duplicate entries in the core namespace (about 5700 entries in all).
I don’t know if this happens in upgrade setup or in lexicon reload. Probably the latter, since I checked and it doesn’t effect any other tables that get values merged on upgrade setup.
Is it safe to just empty the lexicon_entries table and then "reload" in Lexicon Management?

Yeah, that may be due to upgrades, and the instable nature of SVN. It is definitely safe and okay to just empty it and run a reloadFromBase call from Lexicon Management.

Quote from: OpenGeek at Oct 22, 2008, 06:10 PM

That must be a problem with the reload, as I’m not seeing this anywhere. Though, just to be sure, duplicates would be same name, topic, and language; can you confirm you have duplicates in the same topics?

Yes, they’re exact dupes except for the ID and createdon date. Some topics don’t have any, some topics have some keys duplicated and others not. In all cases where there are dupes, there are exactly three copies of the duplicated entries.

I just did two reloads and two upgrade installs (one without a build, one with) and didn’t get any more entries so either it only happens under certain circumstances or it’s been fixed.