Image Wells, Core Data, and Sqlite files.

Question

I've got a mac application that I've developed.

I use it to create sqlite files that are bundled with my iphone app. The mac app uses Core Data and bindings and is working fine except for one "weird" issue.

I use an NSImageView (or Image Well) to allow me to drag and drop jpg files.

This is bound through to an optional binary attribute in my model class.

For some reason when I drag and drop a 4k jpg file it onto the image well and save the sqlite file. The data saved to the binary column is over 15 times larger than it should be.

Whereas if I use an application like SQLiteManager and add the image into the row in the database. The binary data is the correct (expected size).

File 4k jpg Actual size: 2371. Persisted via Core Data size: 35810.

Can anyone give me a suggestion as to why this might be happening?

Do I need to set some setting in Interface Builder or write some custom code?

Answer 1

Create dump from sqlite3 file and check which content use your space. I use plain sqlite3 to store image cache in Galileo and as far i know there db size ~ total images size.