error when destroying record about mobility-actiontext

[arusa]

I successfully implemented this gem, but when I wrote my tests I realized the same error message when destroying objects:

ActiveRecord::StatementInvalid: PG::UndefinedColumn: ERROR:  column mobility_text_translations.record does not exist
LINE 1: ...ations".* FROM "mobility_text_translations" WHERE "mobility_...

[francescob]

I ended up adding that record column on mobility_text_translations table, it's completely useless, but at least it works

[sedubois]

Indeed the Action Text backend is an extension of the Key-Value backend. Also see info in the README implementation note. I haven't needed to delete such records in my app yet, so it's quite possible there are bugs. Don't hesitate to propose a PR with tests!

This is the code in Mobility:
https://github.com/shioyama/mobility/blob/687726d4bab774067da29efc7ade311a71260dcb/lib/mobility/backends/active_record/key_value.rb#L194-L200

It was written by @shioyama in this PR. @shioyama any idea why it's [translation_class, *Mobility::Backends::ActiveRecord::KeyValue::Translation.descendants].uniq? In the case of Action Text should it not be something like [translation_class, *translation_class.descendants].uniq?

[vutran0111]

I got the same problem, can you guys have a solution for this case?

[shioyama]

The reason it's *Mobility::Backends::ActiveRecord::KeyValue::Translation.descendants].uniq is so that if you define your own translation classes subclassing Mobility::Backends::ActiveRecord::KeyValue::Translation, e.g. a translation class for an integer translation, it would still correctly destroy those records.

That code destroy should probably be put behind an option that is default on so that ActionText can disable it. I probably tried a bit too hard to keep things clean after bad experiences with Globalize...

[sedubois]

Fixed by #12.