interface builder - Relationships vs. Attributes in Core Data -


Overall, I love core data yet, but there is a pigment in the system that I'm coming back, And the problems that arise when I decide to use relationships instead of attributes.

For example, using cars, let me have the car unit and the manufacturer unit. Ideally, I can have a relationship between them, many cars with a manufacturer, and then when I'm setting up an editing page for cars, choose the manufacturer in NSPopUpButton User for It works, but it does not appear to save any value, so when I reload the editing page for that particular car, the manufacturer appears empty.

Another option to save the data is to make the manufacturer an attribute, and then set the form to the same form (the manufacturer code which is fed into a NSPopUpButton list) Protects the creator in the car's data, but there is no inconsequential connection to connecting the manufacturer back, which is less than ideal.

How do you make the most effective use of relationships and attributes in core data? Apart from this, how do you solve the above mentioned questions, so that you make connections, but the names of the linked items are displayed instead of "no data" or fault notice?

Have you seen this problem only with your NSPopUpButton user interface? It is possible that you have not properly configured your binding, in core data, enough to assign an example of a suitable unit for a relationship. You will not need a different feature to store the relationship.

The first thing I will investigate is that the chosen object is bound to the right relationship.


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

php - Multiple Select with Explode: only returns the word "Array" -

php - jQuery AJAX Post not working -