Re: On NSIncrementalStore UUID Uniqueness

> Le 19 janv. 2017 à 22:18, Daryle Walker a écrit : > > >> On Jan 16, 2017, at 12:08 PM, Charles Srstka >> wrote: >> >>> On Jan 14, 2017, at 4:41 AM, Daryle Walker >> > wrote: >>> >>> Could I base the UUID off a hash of the URL? Maybe, but it wouldn’t survive >>> fi

Re: On NSIncrementalStore UUID Uniqueness

> On Jan 19, 2017, at 3:18 PM, Daryle Walker wrote: > > >> On Jan 16, 2017, at 12:08 PM, Charles Srstka > > wrote: >> >>> On Jan 14, 2017, at 4:41 AM, Daryle Walker >> > wrote: >>> >>> Could I base the UUID off a hash of the URL? Maybe,

Re: On NSIncrementalStore UUID Uniqueness

> On Jan 16, 2017, at 12:48 PM, Quincey Morris > wrote: > > On Jan 16, 2017, at 09:08 , Charles Srstka > wrote: >> >> The thing with file reference URLs degrading to file path URLs is in the >> Swift is actually not a bug, it’s deliberate >> (https://bugs.swi

Re: On NSIncrementalStore UUID Uniqueness

> On Jan 16, 2017, at 12:08 PM, Charles Srstka wrote: > >> On Jan 14, 2017, at 4:41 AM, Daryle Walker > > wrote: >> >> Could I base the UUID off a hash of the URL? Maybe, but it wouldn’t survive >> file moves. There are file references in macOS, which would be more stab

Re: On NSIncrementalStore UUID Uniqueness

> On Jan 16, 2017, at 3:59 AM, Alastair Houghton > wrote: > > On 14 Jan 2017, at 10:41, Daryle Walker wrote: >> >> Could I base the UUID off a hash of the URL? Maybe, but it wouldn’t survive >> file moves. There are file references in macOS, which would be more stable, >> but I read that th

Re: On NSIncrementalStore UUID Uniqueness

On Jan 16, 2017, at 09:08 , Charles Srstka wrote: > > The thing with file reference URLs degrading to file path URLs is in the > Swift is actually not a bug, it’s deliberate > (https://bugs.swift.org/browse/SR-2728 > ). The Swift team decided that file >

Re: On NSIncrementalStore UUID Uniqueness

> On Jan 14, 2017, at 4:41 AM, Daryle Walker wrote: > > Could I base the UUID off a hash of the URL? Maybe, but it wouldn’t survive > file moves. There are file references in macOS, which would be more stable, > but I read that there’s a bug in the URL class where it would degrade > file-refer

Re: On NSIncrementalStore UUID Uniqueness

On 14 Jan 2017, at 10:41, Daryle Walker wrote: > > Could I base the UUID off a hash of the URL? Maybe, but it wouldn’t survive > file moves. There are file references in macOS, which would be more stable, > but I read that there’s a bug in the URL class where it would degrade > file-reference

Re: On NSIncrementalStore UUID Uniqueness

> On Jan 14, 2017, at 2:32 PM, Jens Alfke wrote: > > >> On Jan 14, 2017, at 2:41 AM, Daryle Walker > > wrote: >> >> I’m seemingly stuck since the data format doesn’t have a UUID field within >> it and I can’t base a UUID off of a hash of the file since it would change

Re: On NSIncrementalStore UUID Uniqueness

> On Jan 14, 2017, at 2:41 AM, Daryle Walker wrote: > > I’m seemingly stuck since the data format doesn’t have a UUID field within > it and I can’t base a UUID off of a hash of the file since it would change > after each edit. There’s really no way to store any custom metadata in the file? I

Re: On NSIncrementalStore UUID Uniqueness

On Jan 11, 2017, at 12:16 PM, Jens Alfke wrote: > >> On Jan 10, 2017, at 2:00 PM, Jean-Daniel wrote: >> >> UUID means Universally unique identifier and it must be unique: >> https://en.wikipedia.org/wiki/UUID >> >

Re: On NSIncrementalStore UUID Uniqueness

> Le 14 janv. 2017 à 11:41, Daryle Walker a écrit : > > >> On Jan 11, 2017, at 3:58 PM, Keary Suska wrote: >> >> >>> On Jan 11, 2017, at 11:16 AM, Jens Alfke wrote: >>> >>> On Jan 10, 2017, at 2:00 PM, Jean-Daniel wrote: UUID means Universally unique identifier and it mus

Re: On NSIncrementalStore UUID Uniqueness

> On Jan 11, 2017, at 3:58 PM, Keary Suska wrote: > > >> On Jan 11, 2017, at 11:16 AM, Jens Alfke wrote: >> >> >>> On Jan 10, 2017, at 2:00 PM, Jean-Daniel wrote: >>> >>> UUID means Universally unique identifier and it must be unique: >>> https://en.wikipedia.org/wiki/UUID >>>

Re: On NSIncrementalStore UUID Uniqueness

> On Jan 11, 2017, at 11:16 AM, Jens Alfke wrote: > > >> On Jan 10, 2017, at 2:00 PM, Jean-Daniel wrote: >> >> UUID means Universally unique identifier and it must be unique: >> https://en.wikipedia.org/wiki/UUID >> >

Re: On NSIncrementalStore UUID Uniqueness

> On Jan 10, 2017, at 2:00 PM, Jean-Daniel wrote: > > UUID means Universally unique identifier and it must be unique: > https://en.wikipedia.org/wiki/UUID > > > To generate an UUID, u

Re: On NSIncrementalStore UUID Uniqueness

On 11 Jan 2017, at 00:16, Saagar Jha wrote: > > Small quibble: UUIDs are not guaranteed to be unique. It's just extremely > likely they will be, and they be sufficient for almost all applications, > including this one. If we’re going to be pedantic, properly issued version 1 and 2 UUIDs *are*

Re: On NSIncrementalStore UUID Uniqueness

Small quibble: UUIDs are not guaranteed to be unique. It's just extremely likely they will be, and they be sufficient for almost all applications, including this one. Saagar Jha > On Jan 10, 2017, at 2:00 PM, Jean-Daniel wrote: > > UUID means Universally unique identifier and it must be uni

Re: On NSIncrementalStore UUID Uniqueness

UUID means Universally unique identifier and it must be unique: https://en.wikipedia.org/wiki/UUID To generate an UUID, use a standard system function (CFUUID, NSUUID, libuuid, …) > Le 10 janv. 2017 à 11:36, Daryle Walker a écrit : > > Been reading up on N

On NSIncrementalStore UUID Uniqueness

Been reading up on NSIncrementalStore, including its guide. I think I grok it more now. When initializing an instance, you're supposed to submit an UUID. Can a single value be used for all instances, or is it supposed to unique per instance? If the latter, and the source data doesn't already ha