http://majid.info/blog/aperture-internals/ Sporadic pontification Fri, 10 Feb 2012 03:47:46 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://majid.info/blog/aperture-internals/comment-page-1/#comment-4866 David Sewell Wed, 04 May 2011 21:54:44 +0000 http://www.majid.info/mylos/stories/2005/12/01/apertureInternals.html#comment-4866 Aha. Thanks for the clarification! Aha. Thanks for the clarification!

]]> http://majid.info/blog/aperture-internals/comment-page-1/#comment-4860 majid Tue, 03 May 2011 21:22:05 +0000 http://www.majid.info/mylos/stories/2005/12/01/apertureInternals.html#comment-4860 Aperture uses Core Data, which is a database-independent abstraction layer, and thus does not use the native SQLite encoding for dates (juliandate), but rather the NSDate format, which should be a double-precision number of seconds since the reference date (2001-01-01 00:00:00 GMT). Aperture uses Core Data, which is a database-independent abstraction layer, and thus does not use the native SQLite encoding for dates (juliandate), but rather the NSDate format, which should be a double-precision number of seconds since the reference date (2001-01-01 00:00:00 GMT).

]]> http://majid.info/blog/aperture-internals/comment-page-1/#comment-4859 David Sewell Tue, 03 May 2011 21:09:05 +0000 http://www.majid.info/mylos/stories/2005/12/01/apertureInternals.html#comment-4859 Thanks for this helpful analysis. I've been looking at Library.apdb (in aperture 3) using an SQLite browser. It mostly makes sense, but I can't for the life of me figure out what is going on with the various time/date values (data type 'timestamp'). They either have single integers that would appear to be Unix seconds-from-epoch values but are not, or else integers separated by '.' that appear to be Julian dates but are way too large. What is up with that? Thanks for this helpful analysis. I’ve been looking at Library.apdb (in aperture 3) using an SQLite browser. It mostly makes sense, but I can’t for the life of me figure out what is going on with the various time/date values (data type ‘timestamp’). They either have single integers that would appear to be Unix seconds-from-epoch values but are not, or else integers separated by ‘.’ that appear to be Julian dates but are way too large. What is up with that?

]]>