Re: [coldsync-hackers] Design logic of Sync conduits

[IwantToKeepAnon <iwanttokeepanon at yahoo dot com>]

"Marco van Beek" <marco@84andahalf.com> writes:

> I have managed to change the {id} number of a palm
record. What I do at the moment is if a record
> is created by the palm, it is added to the MySQL
database where it picks up a new ID number. When
> the sync next runs, the record is added to the Palm
as a new record, and the old one is deleted
> (assuming it hasn't been changed).
>
> When I create the record, I am able to specify the
{id}, which means that the records stay in sync
> across many (so far four) PDA's.

Can I interject?  This seems like a "bad idea"(tm). 
This means that :
  (1) I create a record
  (2) I sync it
  (3) you delete it
  (4) you upload it as a new record (ie. dirty)
  (5) I sync it again

Is that right?

Thats 3 complete transfers where only 1 is needed. 
When you create a
record, Palm allows you to specify an id; but I think
their docs say
*not* to.

I think your DB model may need fixing and not the sync
process.  If
you need to track multiple handhelds/users, just make
the table and/or
keys reflect that.

Ie. for 1 user: PK = record id; works fine.
for 2 users: PK = user id+record id; or PK = record
id+user id

You just need to add user id to the MySQL table.

Lastly the "(assuming it hasn't been changed)" is a
big gap that I
would not be comfortable with and I wouldnt use a
conduit that
read/wrote a single record 3 times.

.... Just my 2 cents.

=====
-- 
"A smile is the shortest distance between two people."
Victor Borge

__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.