osx - Will the core data migration mechanism deal with new data on a pre populated entity? -


i have mac application uses core data 1 entity.

this app creates particles quartz , comes variety of particle setups ready use, fire, smoke, comet, etc. these particles saved on entity , shipped user, or in other words, application comes pre populated entity.

this same entity used save particles created user (i have flag set know if particles created user or me).

i update app including more pre populated particles.

the problem every user has saved particles. need new version not mess , add new particles create them.

i know core data mechanism more suited migrate structures data? suspect core data not that, have check database see if new particles there , add them code first time user runs app, right? or there way automatically?

short answer no. migrations structural changes only. not add new data.

the creation of new data or updating of old data ios business decision , outside of scope of migration api.


Comments

Post a Comment

Popular posts from this blog

toolbar - How to add link to user registration inside toobar in admin joomla 3 custom component -

im trying write component admin side , need add user creation. dont want duplicate existing codes add link. know how add task not simple link toolbar. thx help. if wanting button opens new user screen can try in component: $bar = jtoolbar::getinstance('toolbar'); $bar->appendbutton('link', 'users', 'new user','index.php?option=com_users&task=user.add'); you need add view.html.php file wherever you're creating toolbar. is need?
Read more

linux - disk space limitation when creating war file -

i have 1 gb disk space limitation hosting app , have used 700mb of it. however want create war file directory big (around 600mb) using command : jar -cvf root.war folderpath that's why encounter quota limitation , can't following. i'm looking way delete folder content when it's applying archive conserve disk space take note can't install zip tool in ssh shell ~ the code works on test directories, test first anyway, deletes files. it's not efficient. assumptions: 300mb free space, in destructively compress 600mb folderpath directory. none of files big -- if file in folderpath 300mb or larger, fail. notes: if ' $out ' file exists, nothing. first find pipes file list while , if ' $out ' doesn't exist in loop, create it, don't update -- if does exist, update it. each pass adds 1 more file, deletes unless file directory. after loop finishes delete empty directories too. unset u ; in=folderpath ; out=roo...
Read more