Originally Posted by whpalmer4
Blowing away the database on MobileMe and resyncing just copies a fresh copy of what you have on the client doing the sync. If that client doesn't have a compacted database, or has a bunch of disconnected transactions, the new copy on MobileMe will be the same way. It will fix cases where the MobileMe copy was corrupted (someone/something went and deleted or changed some files in the package) but it won't cause the compaction to happen.
This is just about becoming more trouble than it is worth.
I have a brand new database with about 20 tasks and 4 projects in it created on 1.5. I have OF on my iphone3G but forget about that for now. I simply go
to sync my newly created, apparently overly fat for some reason, database with Webdav OR MM and it takes longer than 30 mins.
Now this "smoosher" is a script that will, or will not compress the database?
Why when we are dealing with low speed devices like WIFI and broadband
would this compression not already be built in as a standard exit "clean-up"
process? Instead we are putering with syncing to MM, it is newest, delete
local copy, sync with MM, sync with Iphone, you are good for a few days?
When writing an application that maintains a database, yes I do keep in mind
the size of the database for optimization when customers are using high speed, and expecially when using low speed devices.
Well, at least I have no need to pay for MM, Bingodisk, or any others.
Local sync is not an option, WIFI not allowed. So it is either MM or WebDav.
I would say that OF is really just a laptop solution. Too many issues from
speed of an inbox (yes with autosync off) it is still slower than a index card INBOX. I have a database size issue with 4 projects and 20 tasks.
You know a new database with one Inbox entry took 22 mins to sync. :(