Of course objects can be saved. . . Sqlite is a lightweight database. . If you use Sqlite, you can only find the data and then alloc the OC object and then assign it. . . If you want to achieve automation, you can consider CoreData
It can be saved. If it were me, I would use JSON to transfer it. When it is entered into the database, it will be a JSON string, and when it is taken out, it will be transferred to the object. Others are also available, it depends on your preference.
If you want to save trouble, you can use Realm to directly access objects. Of course there are shortcomings and pitfalls. We have been using it in a production environment for 2 years
Use realm, oo database, sqlite is a little troublesome and requires Model and DB to convert each other. But swift does not support reflection, so you either have to write the conversion process by hand, or the Model inherits NSObject
Of course objects can be saved. . . Sqlite is a lightweight database. . If you use Sqlite, you can only find the data and then alloc the OC object and then assign it. . . If you want to achieve automation, you can consider CoreData
It can be saved. If it were me, I would use JSON to transfer it. When it is entered into the database, it will be a JSON string, and when it is taken out, it will be transferred to the object. Others are also available, it depends on your preference.
If you want to save trouble, you can use Realm to directly access objects. Of course there are shortcomings and pitfalls. We have been using it in a production environment for 2 years
You can use fmdb to find the data and convert it into a dictionary array, and then convert the dictionary into a model. This is how I usually do it
Use realm, oo database, sqlite is a little troublesome and requires Model and DB to convert each other. But swift does not support reflection, so you either have to write the conversion process by hand, or the Model inherits NSObject