There are a lot of people who go on this journey, and I don't recommend it. If
you want to take advantage of iCloud, it's best to use Core Data directly,
perhaps with an API shim of your own making that makes it easier and more
suitable to your needs.
On Apr 25, 2015, at 12:41 PM, Jeff M
On 25 Apr 2015, at 20:41, Jeff M wrote:
>> On Apr 24, 2015, at 2:44 AM, Simon Slavin wrote:
>>
>> On 24 Apr 2015, at 6:59am, Jeff M wrote:
>>
>>> I don't need to map SQLite to iCloud -- I only need to map SQLite to Core
>>> Data. Core Data then takes care of the iCloud issues.
>>
>> I
> On Apr 24, 2015, at 2:44 AM, Simon Slavin wrote:
>
> On 24 Apr 2015, at 6:59am, Jeff M wrote:
>
>> I don't need to map SQLite to iCloud -- I only need to map SQLite to Core
>> Data. Core Data then takes care of the iCloud issues.
>
> I imagine you'd do that by writing a VFS which used
On 24 Apr 2015, at 6:59am, Jeff M wrote:
> I don't need to map SQLite to iCloud -- I only need to map SQLite to Core
> Data. Core Data then takes care of the iCloud issues.
I imagine you'd do that by writing a VFS which used Core Data for storage.
Core Data could store your data in any of
On Apr 23, 2015, at 3:51 PM, Simon Slavin wrote:
>
> On 23 Apr 2015, at 9:29pm, Jeff M wrote:
>
>> Has there been any discussion about integrating sqlite with Apple's iCloud,
>> either by using Apple's Core Data as the Virtual Machine's database engine
>> (so the VM would operate on Core
On 23 Apr 2015, at 9:29pm, Jeff M wrote:
> Has there been any discussion about integrating sqlite with Apple's iCloud,
> either by using Apple's Core Data as the Virtual Machine's database engine
> (so the VM would operate on Core Data objects) or by otherwise modifying the
> existing
Data (sqlite)) <-->
iCloud.
What is the feasibility of making sqlite a wrapper for Core Data, or
integrating iCloud directly into sqlite? Crazy?
Jeff
7 matches
Mail list logo