Storing data locally

Mac OS X will not automatically load everything in the resources directory into RAM. So don't be concerned about the SQLite database being in the resources directory.

Except...

This isn't good practice. The best practise IMHO would be to have the database in ~/Library/Caches/Blah/, where Blah is a directory with the same name as the bundle identifier of your application (something like com.mycompany.myapp).

Include an empty SQLite database in the resources folder as you planned, but don't put any data into it. Instead, when your application launches create the ~/Library/Caches/Blah directory and copy the SQLite database from your resources directory (if they don't exist already) and then use the database in the Caches subdirectory.

BTW You can get the full, "future-proof" path to ~/Library/Caches with code like this:

Code:

NSArray *array = 
    NSSearchPathForDirectoriesInDomains(
        NSCachesDirectory,
        NSUserDomainMask,
        YES);
NSString *pathString = [array objectAtIndex: 0];

 

Ahh, I've just read your original post more carefully.

The files in the Resources folder inside your XCode project, don't end up in your application's executable. Mac OS X (and iOS for that matter) is different from other operating systems with respect to how applications are package.

What you see as an application icon, in say /Applications, is not a single file, but a directory. If you control+click on these and choose "Show Package Contents" you can see the files within the application.

The files in the Resources folder are copied in to the Contents/Resources directory within your application when XCode builds.

Check out the Bundle Programming Guide in the developer docs. The Bundle Structure section goes into detail about the directories and files within a Mac OS X application. There's also a section titled Accessing a Bundle's Contents which will help you access the SQLite database file.