Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Creating a new implementation of NSPersistantStoreCoordinator to use a different backend?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Creating a new implementation of NSPersistantStoreCoordinator to use a different backend?

Subject: Re: Creating a new implementation of NSPersistantStoreCoordinator to use a different backend?
From: Sherm Pendley <email@hidden>
Date: Thu, 20 Jul 2006 16:12:22 -0400

On Jul 20, 2006, at 3:57 PM, jarrod roberson wrote:

I am writing a Objective-C "binding" to Xapian. ( www.xapian.org )
I decided would like to create a Core Data implementation as well, and can't find anything on creating a new implementation of a backing store.


Get in line: <http://bugreporter.apple.com>, and file a feature request.

It's been filed before, probably quite a few times - I filed one about this myself, when Tiger was still in beta - but I've heard that Apple uses the number of duplicate reports to help prioritize things.

sherm--

Web Hosting by West Virginians, for West Virginians: http://wv-www.net
Cocoa programming in Perl: http://camelbones.sourceforge.net


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



References:  
  >Creating a new implementation of NSPersistantStoreCoordinator to	use a different backend? (From: "jarrod roberson" <email@hidden>)




Prev by Date:
Re: Environment/permissions on NSTask-launched app

Next by Date:
Re: KVO and the observeValueForKeyPath bottleneck

Previous by thread:
Creating a new implementation of NSPersistantStoreCoordinator to	use a different backend?

Next by thread:
menu:updateItem:atIndex:shouldCancel: Crazy instead of Lazy!

Index(es):

Date
Thread