Skip navigation.
 
mlRe: CoreData Best Practices
FROM : Chris Hanson
DATE : Sat Apr 30 00:56:54 2005

On Apr 29, 2005, at 3:29 PM, John Timmer wrote:
> Stick an order key in every author, and use that to sort an array
> created
> out of the set.  This seems better, but commits you to having a unique
> author instance for every place an author appears.


It sounds like you need this anyway since earlier in your post you said
there are essentially no ways of identifying when two authors are
identical.

  -- Chris

Related mailsAuthorDate
mlCoreData Best Practices James Clause Apr 29, 16:49
mlRe: CoreData Best Practices John Brownlow Apr 29, 17:36
mlRe: CoreData Best Practices Scott Stevenson Apr 29, 19:07
mlRe: CoreData Best Practices John Timmer Apr 29, 22:34
mlRe: CoreData Best Practices John Timmer Apr 29, 23:28
mlRe: CoreData Best Practices Bill Bumgarner Apr 30, 00:00
mlRe: CoreData Best Practices John Timmer Apr 30, 00:29
mlRe: CoreData Best Practices Scott Ellsworth Apr 30, 00:43
mlRe: CoreData Best Practices Chris Hanson Apr 30, 00:56
mlCoreData: Single coordinator, multiple contexts? Paul Mix Apr 30, 01:03
mlRe: CoreData Best Practices John Timmer Apr 30, 01:13
mlRe: CoreData: Single coordinator, multiple contexts? Scott Stevenson Apr 30, 01:15
mlRe: CoreData Best Practices Scott Stevenson Apr 30, 01:18
mlRe: CoreData: Single coordinator, multiple contexts? mmalcolm crawford Apr 30, 01:47
mlRe: CoreData Best Practices Bill Bumgarner Apr 30, 09:49
mlRe: CoreData: Single coordinator, multiple contexts? Paul Mix Apr 30, 16:38
mlRe: CoreData: Single coordinator, multiple contexts? mmalcolm crawford May 1, 00:09