我在一个快速的应用程序中使用realm.io。这是我第一次运行迁移,因为我有一个生产中的应用程序。我改变了其中一个模型并添加了几个额外的字段。
我按照文档中的示例进行了操作,然后引用了github repo的示例,当时它不起作用。我认为它可能比文档中的示例更加复杂。
这是我在appdelegate.swift文件中的内容:
func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool {
print ("i'm in here")
// Override point for customization after application launch.
// Inside your application(application:didFinishLaunchingWithOptions:)
window = UIWindow(frame: UIScreen.mainScreen().bounds)
window?.rootViewController = UIViewController()
window?.makeKeyAndVisible()
// copy over old data files for migration
let defaultPath = Realm.Configuration.defaultConfiguration.path!
let defaultParentPath = (defaultPath as NSString).stringByDeletingLastPathComponent
if let v0Path = bundlePath("default-v0.realm") {
do {
try NSFileManager.defaultManager().removeItemAtPath(defaultPath)
try NSFileManager.defaultManager().copyItemAtPath(v0Path, toPath: defaultPath)
} catch {}
}
let config = Realm.Configuration(
// Set the new schema version. This must be greater than the previously used
// version (if you've never set a schema version before, the version is 0).
schemaVersion: 1,
// Set the block which will be called automatically when opening a Realm with
// a schema version lower than the one set above
migrationBlock: { migration, oldSchemaVersion in
// We haven’t migrated anything yet, so oldSchemaVersion == 0
if (oldSchemaVersion < 1) {
// Nothing to do!
// Realm will automatically detect new properties and removed properties
// And will update the schema on disk automatically
}
})
// define a migration block
// you can define this inline, but we will reuse this to migrate realm files from multiple versions
// to the most current version of our data model
let migrationBlock: MigrationBlock = { migration, oldSchemaVersion in
if oldSchemaVersion < 1 {
}
print("Migration complete.")
}
Realm.Configuration.defaultConfiguration = Realm.Configuration(schemaVersion: 1, migrationBlock: migrationBlock)
// Tell Realm to use this new configuration object for the default Realm
Realm.Configuration.defaultConfiguration = config
// Now that we've told Realm how to handle the schema change, opening the file
// will automatically perform the migration
_ = try! Realm()
return true
}
print
永远不会运行,我觉得很奇怪。我搞砸了什么?我假设我一定是。
以下是文档所说的内容,我不确定他们是否会遗漏某些东西:
// Inside your application(application:didFinishLaunchingWithOptions:)
let config = Realm.Configuration(
// Set the new schema version. This must be greater than the previously used
// version (if you've never set a schema version before, the version is 0).
schemaVersion: 1,
// Set the block which will be called automatically when opening a Realm with
// a schema version lower than the one set above
migrationBlock: { migration, oldSchemaVersion in
// We haven’t migrated anything yet, so oldSchemaVersion == 0
if (oldSchemaVersion < 1) {
// Nothing to do!
// Realm will automatically detect new properties and removed properties
// And will update the schema on disk automatically
}
})
// Tell Realm to use this new configuration object for the default Realm
Realm.Configuration.defaultConfiguration = config
// Now that we've told Realm how to handle the schema change, opening the file
// will automatically perform the migration
let realm = try! Realm()
任何想法我做错了什么?
答案 0 :(得分:3)
这最终成为了解决方案。我不能说我自己想出来因为我没有。我得到了一位名叫克莱尔的优秀工程师的出色帮助。
这是需要做的事情:
class RoomsViewController: UIViewController, UITableViewDelegate {
var activeRoom = -1
var room: Room? = nil
var array = [Room]()
lazy var realm:Realm = {
return try! Realm()
}()
var notificationToken: NotificationToken?
@IBOutlet weak var roomsTable: UITableView!
override func viewDidLoad() {
super.viewDidLoad()
array = Array(realm.objects(Room.self))
setupUI()
// Set realm notification block
notificationToken = realm.addNotificationBlock { [unowned self] note, realm in
// TODO: you are going to need to update array
self.roomsTable.reloadData()
}
}
这是第一个被加载的视图控制器,它立即查询领域数据库以构建数组。根据Claire的建议,Realm是懒惰加载(或尝试过)并且构建数组的代码被移动到viewDidLoad方法中,而在顶部调用它之前。
这使得领域可以向前运行。正如您可能想象的那样,我诚实地认为,在application
中加载AppDelegate
函数之后,视图才会被加载。但是,我猜我错了。
所以,这将解决它。如果您碰巧遇到同样的问题,请试一试。
<强>更新强>
以下是appDelegate函数现在的样子:
func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -> Bool {
// Inside your application(application:didFinishLaunchingWithOptions:)
let config = Realm.Configuration(
// Set the new schema version. This must be greater than the previously used
// version (if you've never set a schema version before, the version is 0).
schemaVersion: 1,
// Set the block which will be called automatically when opening a Realm with
// a schema version lower than the one set above
migrationBlock: { migration, oldSchemaVersion in
// We haven’t migrated anything yet, so oldSchemaVersion == 0
if (oldSchemaVersion < 1) {
migration.enumerate(Inventory.className()) { oldObject, newObject in
// No-op.
// dynamic properties are defaulting the new column to true
// but the migration block is still needed
}
migration.enumerate(Profile.className()) { oldObject, newObject in
// No-op.
// dynamic properties are defaulting the new column to true
// but the migration block is still needed
}
migration.enumerate(Room.className()) { oldObject, newObject in
// No-op.
// dynamic properties are defaulting the new column to true
// but the migration block is still needed
}
migration.enumerate(Box.className()) { oldObject, newObject in
// No-op.
// dynamic properties are defaulting the new column to true
// but the migration block is still needed
}
}
})
// Tell Realm to use this new configuration object for the default Realm
Realm.Configuration.defaultConfiguration = config
// Now that we've told Realm how to handle the schema change, opening the file
// will automatically perform the migration
do {
_ = try Realm()
} catch let _ as NSError {
// print error
}
return true
}
答案 1 :(得分:1)
看起来你完全将代码从Realm Swift'Migration'示例中复制出来并逐字粘贴。很多代码都是在每次运行示例应用程序时实际“设置”一个新的演示迁移,而不是实际正常的Realm迁移所必需的。
Realm迁移有两个组件:
将架构版本号压缩到Configuration
对象中。 Realm文件从版本0开始,每次要进行新迁移时,将其增加1。
提供一个迁移块,该块将针对Realm架构版本的每个增量执行多次。虽然块本身是必需的,但它的目的是让您复制/转换旧Realm文件中的任何数据。如果您只是添加新字段,则可以将该块留空。
如果您的UIViewController
在其实施中完全使用Realm,则最好将迁移代码放在UIWindow
代码之前,以确保在UIViewController
开始使用之前已经发生迁移它(否则你会得到一个例外)。
由于你所做的只是为它添加一些字段,这就是你需要的所有代码:
let migrationBlock: MigrationBlock = { migration, oldSchemaVersion in
//Leave the block empty
}
Realm.Configuration.defaultConfiguration = Realm.Configuration(schemaVersion: 1, migrationBlock: migrationBlock)
window = UIWindow(frame: UIScreen.mainScreen().bounds)
window?.rootViewController = UIViewController()
window?.makeKeyAndVisible()
答案 2 :(得分:1)
这可以按预期工作,在降级时抛出异常(如果使用版本不同的分支)等。也会显示一些示例迁移。
Realm.Configuration.defaultConfiguration = Realm.Configuration(
// Update this number for each change to the schema.
schemaVersion: 4,
migrationBlock: { migration, oldSchemaVersion in
if oldSchemaVersion < 2 {
migration.enumerate(SomeObject.className()) { oldObject, newObject in
newObject!["newColumn"] = Enum.Unknown.rawValue
}
}
if oldSchemaVersion < 3 {
migration.enumerate(SomeOtherObject.className()) { oldObject, newObject in
newObject!["defaultCreationDate"] = NSDate(timeIntervalSince1970: 0)
}
}
if oldSchemaVersion < 4 {
migration.enumerate(SomeObject.className()) { oldObject, newObject in
// No-op.
// dynamic properties are defaulting the new column to true
// but the migration block is still needed
}
}
})
显然,不会像SomeObject
等那样编译,但你明白了这一点:)
答案 3 :(得分:0)
我发现这在View Controller中最有效:
let migrationBlock: MigrationBlock = { migration, oldSchemaVersion in
//Leave the block empty
}
lazy var realm:Realm = {
Realm.Configuration.defaultConfiguration = Realm.Configuration(schemaVersion: 1, migrationBlock: migrationBlock)
return try! Realm()
}()
换句话说,将配置分配移到该块中,以免执行得太晚。