"Duplicate key com.luckydroid.mementofx.db.models.FieldTemplate@1dd73120". Compatibility troubles between mobile and desktop versions.

507 views
Skip to first unread message

Tony G

unread,
Jan 1, 2017, 1:15:00 PM1/1/17
to mementodatabase
Hello everyone. 
I love your app and I use it mainly as a lab notebook in organic chemistry. I started creating and using it on my Android Nougat and then tried how it works in a desktop.
And that's the moment when troubles came up.  
One calculation field in a database works absolutely properly in mobile version but shows errors kinda "Duplicate key com.luckydroid.mementofx.db.models.FieldTemplate@1dd73120" for all entries in a desktop version. The text after "@" is unique for every entry and changes anytime I refresh the library. Detailed information in the attachments.
What can it be caused by and how can I fix it? 
Will be grateful for any help.
Desktop 1.0.7.png
Mobile 4.2.0.jpg

IVAN VERACRUZ

unread,
Jan 25, 2017, 3:45:01 AM1/25/17
to mementodatabase
I have the same problem:

"Duplicate key com.luckydroid.mementofx.db.models.FieldTemplate@17f3d5b"

Any one know the solution?

thanks

Bill Crews

unread,
Jan 25, 2017, 8:54:50 AM1/25/17
to mementodatabase
Neither of you show the library structure. Duplicate entry names are OK in general, but if you have set entry name to be unique, it must be. Is it set as unique in the mobile edition also, or only in the desktop edition? If set as unique, Memento will catch nonuniqueness during entry edit, but if you make that setting after some data is already in the library, maybe that causes the error.

Although the developer states that a field name may contain any UTF-8 string, I believe he should not say this, because inclusion of certain characters certainly cause errors in certain situations, and due to the different implementations, the errors may manifest themselves differently in the different editions. Examples include characters like the at sign (@). However, this is FIELD names; ENTRY names are built from field VALUES, and I know of no restriction there.

Tony G

unread,
Jan 30, 2017, 6:22:42 PM1/30/17
to mementodatabase
(Just another Tony G here...)

This is a topic I've been wondering about for a while: How exactly does Memento generate the Entry key?

I was creating a chart that kept aggregating data by Date, and I needed to create a separate DateTime field to keep points separate. I was hoping to just use the EntryID, which would be unique for this library. But I don't see a way to reference the ID field for an Entry. And if that's a GUID or some concatenation of data then it would be long and ugly in charts.

T

Bill Crews

unread,
Jan 30, 2017, 10:01:19 PM1/30/17
to mementodatabase
At the logical level, the entry name (unique if you stipulate it as so), is composed from the fields of the library that are set to display as Entry Name, concatenated with intervening spaces.

Now, at the physical level, Eugene has speculated -- from the sheet column added by Memento when linking to Google Sheets and from other probing he has done -- that there is an entry identifier (that is unique even when/if the entry name is not) that may be precisely that string that each entry generates in that added column during Sheets sync.

Jaay V

unread,
Jan 10, 2018, 12:48:06 AM1/10/18
to mementodatabase
I'm having the same issue. It was working fine one moment, then suddenly it shut down and says "Error loading entries: Duplicate key com.luckydroid.memento.client3.model.FieldValueModel3@"string of numbers. How do I fix this?

Jaay V

unread,
Jan 10, 2018, 1:27:11 PM1/10/18
to mementodatabase
Annnnd suddenly like magic it's fixed! (I did nothing to it, btw.) Maybe this is some sort of glitch in the new update? Memento peeps!! Can you check this out and help us out??
Reply all
Reply to author
Forward
0 new messages