|
Is there a document that describes the recommended way of dealing with schema changes in a Mobilink setup? I found http://dcx.sap.com/sqla170/en/html/81a9817d6ce2101492e8b8285e7791d9.html but even after reading it, I don't know the answers to the following:
|
Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in June and this forum will be retired.
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Question tags:
question asked: 07 Sep '20, 06:47
question was seen: 696 times
last updated: 09 Sep '20, 05:23
Use SAP Mobile Platform... or send a new version of your application to your users. That's why every script has "version".
My pseudo-experience shows that there are always users, who don't update their apps regularly. And you have to invent a model of behavior what to do with them: stop sync for them, push the application from Device Management software, push SQL scripts somehow and apply the change locally.
And yes, mobile development is not that simple :)
The First Rule Of MobiLink Schema Changes is "Don't make any schema changes".
If you choose to ignore that rule, here's an article that may help: Database Synchronization for the Simbex Head Impact Telemetry System
Beck, IIUC your blog post introduces a new table (which is also synchronized via ML) that contains SQL migration scripts. Then there is a bit of infra to actually run the SQL migration script on each remote DB. Biggest question in my mind right now: how come this is not already part of Mobilink? And what exactly does the
Update Schemafunction in the GUI do, if not this?