I have tried the prestage content way to get packages for some of my new distribution point and I was wondering if it was any possibility to get the revision version of the .pkgx application created.
In that way, I will be able to see if my .pkgx have to be updated.
Create a .ini file and save the information you get while creating the .pkgx application (like the revision).
In that case, you'll be able to test the revision and "update" it(delete the .pkgx and create a new one).
Related
Here I've got a question concerning releasing update of the application in app store.
Suppose I've an application installed on my iPhone, which has some database inside, i.e. overtime user has entered info and the data were kept locally.
If the new version of application is released, and installed on my iPhone. Will the database be lost ?
I suppose all the information of the application, is removed and the update is installed like a new app. Please confirm.
Thanks
No the users data will not be lost.
When you update an app only the bundle data will be updated, meaning the .app directory of the installed app. Any other directory, like Documents and Library will not be touched.
If there is any data in for example the Documents directory that need updating then you have to write code to detect that and make the necessary changes.
If the database is used by Core Data then you will need to version and migrate the data.
All the files stored inside your app's documents directory (which is usually where db file is stored) are preserved during app update.
If you would have set the version number to your database for your iphone could have been easily handle, save your version number into your db and whenever database is called, compare the version against the expected version If new version > older version change the schema (this is needed if you would have changed the schema of your database) with using SQL ALTER statements and update the app version number.
so whenever user is going to update or fresh installation, it will check the new version with your older version, if it differ then update schema, and if its same no need to make any changes.
If you would not have made any schema related changes (for example adding new column..) then you do not need to worry, user will not lose the data.
my guess is that it would not be replacing any of the existing files instead just updating them if any changes....the best example of data is not lost is that.....i usually update most of my games. and they do preserve my highscore even after the updates.. lol! So, go on. Nothing will be lost. Nice question though. :)
Our project saves the model in xml resource file. The xml resource tags get listed as nodes in project explorer. This project is part of source control and been worked upon by multiple users. I am able to handle all enotifications and take appropriate actions when user performs the changes in his workspace. Though when other users change the model file, and the new synced file is obtained in other workspace, I get only notification that xml file was modified. What exact model changes were done is not received.
Things work fine if user closes and open the project.Though this is not the right solution. I tried doing resource.unload followed by resource.load.This didn't make any difference. How can I achieve the desired result programmaticaly?
EMF Compare should be able to help you in comparing two files, but I'm not sure if it integrates well with SCMs.
I'm trying to figure out where does webistrano keep its custom recipes (I want to copy them), and I can't seem to locate them. I've scoured the installation folder on the server to no avail.
Does anyone know where they are kept?
They were stored in its backend database.
Recipes created inside the admin interface are stored in the database. The recipes table holds the information for the recipe and the revision to be executed on, include the actual code for the current version. The recipe_versions holds a complete copy of each version of the recipe.
The project types (templates) are created inside the repository at lib/webistrano/template/
I wrote a game that I plan on updating soon. The game generates a scoreboard when the application starts, if there is no scoreboard file present.
If people update to my latest version, will the scoreboard file (that's generated by the code itself, not a file that comes preloaded in the app) be deleted?
If so, is there any way to avoid this without any coding previously required?
The updated version of your app will simply replace the existing version's bundle - any files you've written to your app's document area will remain intact.
As such, you simply need to check for the presence of the file within your app's document area as per usual and write a "new" version if none exists.
If the file is within your applications bundle, it will be deleted. Files saved with Core Data and NSUserDefaults will not. I've never personally written a file to the disk, so I don't know where the default write point is. You'll have to find this out yourself.
Happy coding,
Zane
I have some general questions about iphone app updates that involves sqlite db.
With the new update does the existing sqlite db get overwritten with a copy of the new one?
If the update doesn't involve any schema changes then the user should be able to reuse the existing database with their saved data, right? (if the existing database doesn't get overwritten from 1 above )
If there are some schema changes, what's the best way to transfer data from the old database into the new one? Can some one please give me guidelines and sample code?
Only files inside the app bundle are replaced. If the database file is in your app's Documents directory, it will not be replaced. (Note that if you change files inside your app bundle, the code signature will no longer be valid, and the app will not launch. So unless you are using a read-only database, it would have to be in the Documents directory.)
Yes.
What's best depends on the data. You're not going to find sample code for such a generic question. First, you need to detect that your app is running with an old DB version. Then you need to upgrade it.
To check versions:
You could use a different file name for the new schema. If Version2.db does not exist but Version1.db does, do an upgrade.
You could embed a schema version in your database. I have a table called metadata with a name and value column. I use that to store some general values, including a dataversion number. I check that number when I open the database, and if it is less than the current version, I do an upgrade.
Instead of creating a table, you could also use sqlite's built-in user_version pragma to check and store a version number.
You could check the table structure directly: look for the existence of a column or table.
To upgrade:
You could upgrade in place by using a series of SQL commands. You could even store a SQL file inside your app bundle as a resource and simply pass it along to sqlite3_exec to do all the work. (Do this inside a transaction, in case there is a problem!)
You could upgrade by copying data from one database file to a new one.
If your upgrade may run a long time (more than one second), you should display an upgrading screen, to explain to the user what is going on.
1) The database file isn't stored as part of the app bundle so no, it won't get automatically overwritten.
2) Yes - all their data will be saved. In fact, the database won't get touched at all by the update.
3) This is the tricky one - read this fantastically interesting document - especially the part on lightweight migration - if your schema changes are small and follow a certain set of rules, they will happen automatically and the user won't notice. however, if ther are major changes to the schema you will have to write your own migration code (that's in that links as well)
I've always managed to get away with running lightweight migrations myself - it's by far easier than doing it yourself.
What I do is that I create a working copy of the database in the Documents directory. The main copy comes with the bundle. When I update the app I then have the option to make a new copy over the working copy, or leave it.