> On Aug 25, 2014, at 1:21 PM, Tim Anglade wrote:
>
> We did publicly commit to open-sourcing the core under the Apache 2.0
> license [1].
I had not seen that FAQ when I did my initial evaluation of Realm about a month
ago. Thanks for pointing it out, and I'm glad to hear you'll be opening the
On Aug 23 2014 at 11:37 AM, Jens Alfke wrote:
I would not feel comfortable shipping an app based on a database
engine whose source isn't available, where there's no information
about future support, and which has an unknown track record of
stability.
Hi, Tim from Realm here.
We did publicly c
We developed a simple BFWQuery class for accessing SQLite databases as if they
were NSArrays. It is designed to make it simple for Cocoa developers to get up
and running without sacrificing any of the power of SQLite. It uses FMDB under
the hood.
It might be useful for you.
https://github.com/
If you are going to go the core data route, you should look into using it with
this most excellent tool:
https://github.com/rentzsch/mogenerator
Shane
Sent from my iPhone
> On Aug 22, 2014, at 7:25 PM, Jim Geist wrote:
>
> I don’t know of any storage quotas, I’ve seen debug logging fill up
> On Aug 23, 2014, at 9:57 AM, Carl Hoefs
> wrote:
>
> However, specifically on iOS, I take it that SQLite is the *only* database
> available
It's the only one built into the OS with a public API. But there are a lot of
options if you're willing to build and link in your own database — Tokyo
From Realm home page: "Realm is not built on SQLite."
On 23 Aug 2014, at 17:57, Carl Hoefs wrote:
>
> On Aug 23, 2014, at 9:23 AM, Glenn L. Austin wrote:
>
>> CoreData is not a database (according to Marcus Zarra -- and he should
>> know). Even though it *can* use an SQLite data store (and
On Aug 23, 2014, at 9:23 AM, Glenn L. Austin wrote:
> CoreData is not a database (according to Marcus Zarra -- and he should know).
> Even though it *can* use an SQLite data store (and most people do that), it
> doesn't depend upon SQLite functionality.
However, specifically on iOS, I take i
CoreData is not a database (according to Marcus Zarra -- and he should know).
Even though it *can* use an SQLite data store (and most people do that), it
doesn't depend upon SQLite functionality.
SQLite is built-in and available pretty much everywhere, but you need to learn
a bit of SQL.
On A
There is also YapDatabase https://github.com/yaptv/YapDatabase -- a KV-store
built atop SQLite.
On 23 Aug 2014, at 16:17, Carl Hoefs wrote:
> Wow, I didn’t realize there were so many options. I’ll be looking into all of
> these (SQLite, CoreData, FMDB, Realm) to see which fits into my project'
Wow, I didn’t realize there were so many options. I’ll be looking into all of
these (SQLite, CoreData, FMDB, Realm) to see which fits into my project's
design best (and which appeals to me).
Thanks for all the great suggestions!
-Carl
___
Cocoa-dev
FMDB is also a very popular and simple Objective-C wrapper to SQLite
You can be up and running with it in minutes.
And it works on OS X the same so it's portable.
Sent from my iPhone
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do n
I would recommend taking a look into the newly released Realm
(http://realm.io). I’ve been using it for the last couple of weeks and I’d bet
it’s a solid alternative to SQL base databases / ORMs (SQLite). APIs are really
easy to grasp and queries to the database are human-friendly and powerful.
I'm not sure how helpful this is but rechnically, Core Data is an ORM - an
object to relational mapping framework. Also realize that Core Data is most
often configured to use SQLite as its backing store. In addition the, Xcode
ships with a nice CoreData/ORM editor which often makes Core Data eas
2 choices out of the box - Core Data and SQLite
Core data (once learnt) saves you a lot of time writing cookie cutter code.
As for storage - the iOS platform obviously has storage limitations by device
so if you’re going to target 8GB devices you’ve already got a limit but within
reason an app
I don’t know of any storage quotas, I’ve seen debug logging fill up the device
before the app gets whacked. And some of the games I play have gigs of data.
CoreData has a bit of a curve, but it saves you a lot once you’re used to it.
It works at the object level, and just not having to serialize
On Aug 22, 2014, at 6:01 PM, Jim Geist wrote:
> Can you use CoreData?
On Aug 22, 2014, at 6:00 PM, Catchall wrote:
> Is there a reason to not use CoreData?
Hmm, I guess that’s what CoreData is for, isn’t it? I had heard that it is
pretty difficult to learn, and since I’m used to accessing d
Can you use CoreData?
On Aug 22, 2014, at 5:54 PM, Carl Hoefs wrote:
> I’m writing a Cocoa-based iOS 8 app that needs to store and manage data
> locally on the device. Is there a relational database available for general
> purpose use in iOS 8? Is there a limitation to how much space an app ca
I’m writing a Cocoa-based iOS 8 app that needs to store and manage data locally
on the device. Is there a relational database available for general purpose use
in iOS 8? Is there a limitation to how much space an app can use in its
sandbox? I presume a database would necessarily need to reside i
18 matches
Mail list logo
