CoreStoreObject, Relations and migration #205

New Issue

Open

opened 2025-12-29 18:24:21 +01:00 by adam · 1 comment

adam commented 2025-12-29 18:24:21 +01:00

Owner

Copy Link

Copy Source

Originally created by @SlinToWin on GitHub (Apr 23, 2018).

Hello,

i have a large CoreData Schema with round about 30 Entities and several relations. Implementation was done via CoreStoreObject

Now i want to add a property to one of my CoreStoreObjects.
Following the guide i created two Versions of my object, V1 and V2 and also created a typealias for the Name, so that i dont have to change all source files, where the object was used.

The Object has a relation to another CoreStoreObject. With this two Versions and the typealias, the build will fail because the inverse of the other CoreStoreObject cant be mapped to V1.
So i have to create also two versions for that one. This has relations to other Objects so i have to create also versions for that.

End of story is, that i have to create V2 for all 30 CoreStoreObjects, although only one object was changed because of the relations.

Is there any better way for doing that with CoreStoreObject (so that i just have to create Versions for Objects, which i really change?)

Originally created by @SlinToWin on GitHub (Apr 23, 2018). Hello, i have a large CoreData Schema with round about 30 Entities and several relations. Implementation was done via CoreStoreObject Now i want to add a property to one of my CoreStoreObjects. Following the guide i created two Versions of my object, V1 and V2 and also created a typealias for the Name, so that i dont have to change all source files, where the object was used. The Object has a relation to another CoreStoreObject. With this two Versions and the typealias, the build will fail because the inverse of the other CoreStoreObject cant be mapped to V1. So i have to create also two versions for that one. This has relations to other Objects so i have to create also versions for that. End of story is, that i have to create V2 for all 30 CoreStoreObjects, although only one object was changed because of the relations. Is there any better way for doing that with CoreStoreObject (so that i just have to create Versions for Objects, which i really change?)

adam added the question label 2025-12-29 18:24:21 +01:00

adam commented 2025-12-29 18:24:22 +01:00

Author

Owner

Copy Link

Copy Source

@JohnEstropia commented on GitHub (Apr 24, 2018):

End of story is, that i have to create V2 for all 30 CoreStoreObjects, although only one object was changed because of the relations.

In reality, relationship targets are also part of the data and will affect the versioning hash, so any updated entities will affect all related objects. How will an object know which version of it's relationship is it holding?

This replication is the same when you create a new version from an xcdatamodeld; all entities are always reflected on the new versions. The solution is also as simple as how xcdatamodeld does it:

1. Copy the old entities
2. Paste them on the new version
3. Edit the new version
4. Avoid editing the old version (i.e. VersionLock)

@JohnEstropia commented on GitHub (Apr 24, 2018): > End of story is, that i have to create V2 for all 30 CoreStoreObjects, although only one object was changed because of the relations. In reality, relationship targets are also part of the data and will affect the versioning hash, so any updated entities will affect all related objects. How will an object know which version of it's relationship is it holding? This replication is the same when you create a new version from an `xcdatamodeld`; all entities are always reflected on the new versions. The solution is also as simple as how `xcdatamodeld` does it: 1. Copy the old entities 2. Paste them on the new version 3. Edit the new version 4. Avoid editing the old version (i.e. `VersionLock`)

adam referenced this issue 2025-12-29 18:27:12 +01:00

[PR #205] [MERGED] add case-insensitive sortkeys #475

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

develop

prototype/swift6

master

prototype/concurrency

minIOS13

prototype/containers

transactionSourceTracking

prototype/swiftui

minIOS11

swift5_3

prototype/propertyWrapperFields

prototype/propertyWrappers

prototype/propertyWrapper

Swift5

throwables

prototype/Swift_4_1

prototype/Swift_4_0

prototype/Swift_3_2

prototype/queryBuilders

temp/develop

corestore4_develop

prototype/mainContextToPSC

master_ios_7_to_9

swift_2_3

gh-pages

_corespotlight-test

9.3.0

9.2.0

9.1.0

9.0.0

8.1.0

8.0.1

8.0.0

7.3.1

7.3.0

7.2.0

7.1.0

7.0.4

7.0.3

7.0.2

7.0.1

7.0.0

6.3.2

6.3.1

6.3.0

6.2.1

6.2.0

6.1.0

6.0.0

5.3.1

5.3.0

5.2.0

5.1.1

5.1.0

5.0.0

4.2.4

4.2.3

4.2.2

4.2.1

4.2.0

4.1.4

4.1.3

4.1.1

4.1.0

4.0.5

4.0.4

4.0.3

4.0.2

4.0.1

4.0.0

4.0.0-beta3

4.0.0-beta2

4.0.0-beta

3.1.1

3.1.0

3.0.3

3.0.2

3.0.1

3.0.0

2.1.3

2.1.2

2.1.1

2.1.0

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.1

2.0.0

1.6.10

1.6.9

1.6.8

1.6.7

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.1

1.2.0

1.0.2

1.0.1

1.0.0

0.2.1

0.2.0

0.1.2

0.1.1

0.1.0

Labels

Clear labels

abandoned

corestore bug

discussion

duplicate

enhancement

fixed

fixed

help wanted

in progress

investigating

ios/compiler bug

irreproducible

looking for workarounds

not a bug

pending

pending docs update

pull-request

Mirrored from GitHub Pull Request

question

regression

user bug

wontfix

No labels question

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

adam (Adam Melkus)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/CoreStore-JohnEstropia#205