Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

recordName index not being created. #83

Open
daviddelmonte opened this issue Apr 10, 2018 · 5 comments
Open

recordName index not being created. #83

daviddelmonte opened this issue Apr 10, 2018 · 5 comments

Comments

@daviddelmonte
Copy link

daviddelmonte commented Apr 10, 2018

In the demo app, a recordName index appears to be created for each device / event. Can you briefly point me to where that index is made. I cannot get this index built in my apps.

However, even in the demo app, the recordName index is not queryable. Is it possible to automatically make this happen?

Thanks

@ghost
Copy link

ghost commented Jan 2, 2019

I would appreciate this info too. Just need to work with recordName to skip the 1:750 reference limit. Thanks

@ghost
Copy link

ghost commented Jan 8, 2019

Ok maybe I am wrong but what I have found with reverse analysis is that there is process of creation of submodel which stores the recordName under "sm_LocalStore_RecordID" key, more generally with use of SMStore.SMLocalStoreRecordIDAttributeName string value. These values are added in the addExtraBackingStoreAttributes method to the entity and lately in the sync process removed from the entity again. My idea would be to keep these attributes in the entity, however the stupid solutions I was able to try (like editing of specific code in the Seam3 to achieve it) failed. Any suggestions?

@paulw11
Copy link
Owner

paulw11 commented Jan 8, 2019

@daviddelmonte Where do you see the index? As @rajtrj points out, Seam3 does index the sm_LocalStore_RecordID attribute that it creates

@daviddelmonte
Copy link
Author

I'm trying to remember what I did. iirc, I ended up making my own index -- but if you could index sm_LocalStore_RecordID, that would likely solve a key data sync issue that bites me from time to time. First thing tomorrow, when I'm home, I'll pull out the code again.

@ghost
Copy link

ghost commented Jan 9, 2019

@daviddelmonte Where do you see the index? As @rajtrj points out, Seam3 does index the sm_LocalStore_RecordID attribute that it creates

Unfortunately - as far as I understand it - it is created on the level of CoreData submodel so it is not accessible direct way, am I correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants