[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [coldsync-hackers] Design logic of Sync conduits
What about letting the Handheld assign its own record id and the Server use
its SQL ids, and then, for each Handheld, have a SQL table containing
(Database,hhID,sID), where Database is the name of the Handheld database
(DatebookDB, etc), hhID is the handheld record ID for that database, and
sID is the server record ID (which might be database specific or it could
be a global ID).
Aha! - How about adding the Palm Serial Numbers numbers the table (so
four fields, but only one table). This means I could look at using the
user name properly as an ownership / responsibility field, as we could
work by Palm Serial Number.
Your idea also brings about a much better possibility of relating
records between different tables as well. I had been playing around with
the idea of assigning each regular client (we don't have that many!) a
category in each app, and having a sort of lookup that way.
It would also be possible to have a dirty field, as there would be a
unique record for every single Palm record, no matter how big it all
got. As long as the MySQL database has a large enough ID field (and I
tend to use 11 character ID fields, verses 8 (I think, without looking)
in the Palm), it should scale really well.
I always like having separate "people" and "company" tables, with
personal data in one, and corporate data in the other. I have tended to
use the Palm "Main Number" field as the switchboard, and "Work" as the
direct line number.
I think we may have a solution. All I have to do now is code it...
Thanks for all the help. I will re-write my strategy and post it to the
list later.
Regards,
Marco.
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.