Re: which cocoa wrapper for sqlite should i get?

FROM : Paul Lynch
DATE : Mon Jun 05 18:18:10 2006

On 5 Jun 2006, at 16:37, kyle kinkade wrote:

> too me it feels like with Core Data you didn't really have too much 
> control with the data. it seemed like you built your models, 
> plugged everything together with interface builder, and that was 
> it, but i really wanted more from it, in the sense of having more 
> direct access. and the resulting database file would need to be 
> exchanged with other platforms.
>
> or maybe i'm interpreting Core Data wrong?


I would say so, yes.

You can get as much control over the objects as you want.  Core Data 
can be difficult to grasp if your background is JDBC/SQL (etc), but 
being able to view the data as part of an object model is very 
compelling.

It might help if you took a look at the "Low Level" Core Data 
tutorial on the ADC site; that is probably a more appropriate 
introduction for someone already familiar with other low level APIs.

Other platforms should be able to read your database; but you may 
have problems using Core Data on an SQLite database created elsewhere.

Paul


> On Jun 5, 2006, at 8:31 AM, Paul Lynch wrote:
>

>>
>> On 5 Jun 2006, at 16:21, kyle kinkade wrote:
>>

>>> so many choices, so little dev time.
>>>
>>> i've heard of several sqlite wrappers for cocoa and i'm wondering 
>>> if any of you have used one you prefer. or if you prefer one at 
>>> all...
>>>
>>> sqlite... cocoa... can they live together in harmony?

>>
>> So; what's wrong with CoreData?
>>
>> If you need to support 10.3 or earlier, or need to exchange 
>> databases with other platforms, you should probably take a look at 
>> QuickLite.  I have used it and it seems solid, with reasonable 
>> integration with Cocoa concepts.
>>
>> Paul

>
>