pilot-db-list

How do you update [Was: Re: [pilot-db-list] current 0.3.x status

[Larry W. V. <lv...@ca...>]

Tom, this is such great news!  I really want to thank you for your hard
work on this.

I have a question for you other DB users.

I have built a series of inventory like databases.  I have not yet figured
out the best way though to distribute updates to these databases.
If a user installs one of these databases as I distributed them and
then uses them, they lose any data they might have entered into the 
database if I have an update to send out that contains say new items,
renamed inventory items , etc.

This is _sort_ of a sync-ing type issue.  Has anyone investigated
syncing for DB?
-- 
Larry W. Virden <mailto:lv...@ca...>
<URL: http://www.purl.org/NET/lvirden/>
Unless explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-

Re: How do you update [Was: Re: [pilot-db-list] current 0.3.x status

[Tom D. <td...@vg...>]

On Wed, 12 Apr 2000, Larry W. Virden wrote:

> I have built a series of inventory like databases.  I have not yet figured
> out the best way though to distribute updates to these databases.
> If a user installs one of these databases as I distributed them and
> then uses them, they lose any data they might have entered into the 
> database if I have an update to send out that contains say new items,
> renamed inventory items , etc.

I'm not sure even HotSync could handle this type of sync'ing. Imagine if
you distributed text files to be viewed in MemoPad. If the file is
modified on both the Pilot and the desktop, then HotSync usually
duplicates the file and says for the user to resolve the issue. 

There has to be a better way though. Maybe a merge option in DB or
something. Not sure what form it would take. Probably needs some
brainstorming.

Tom

Re: How do you update [Was: Re: [pilot-db-list] current 0.3.x status

[Hal D. <hal...@ea...>]

>>>>> On Wed, 12 Apr 2000, "Tom" == Tom Dyas wrote:

  Tom> If the file is modified on both the Pilot and the desktop,
  Tom> then HotSync usually duplicates the file and says for the
  Tom> user to resolve the issue.

But, OTOH, if you add appointments using both the desktop and the
Palm, then the entire datebook is NOT duplicated.

All depends on the conduit and the "granularity" of the sync.  
With memos, an entire memo is an "item" for syncing.  With the 
datebook an individual appointment is an "item".

Conceptually there doesn't seem any reason that an individual 
database RECORD couldn't be the "item".  Easy for me to say 
since I've never done any Palm or conduit development.

--Hal

Re: How do you update [Was: Re: [pilot-db-list] current 0.3.x status

[Tom D. <td...@vg...>]

On Wed, 12 Apr 2000, Hal DeVore wrote:

> All depends on the conduit and the "granularity" of the sync.  
> With memos, an entire memo is an "item" for syncing.  With the 
> datebook an individual appointment is an "item".

Implied. I did a modification to a phone book entry on my Palm III and the
desktop and just the entry itself was duplicated. 

> Conceptually there doesn't seem any reason that an individual 
> database RECORD couldn't be the "item".  Easy for me to say 
> since I've never done any Palm or conduit development.

But then the duplication problem still exists. If user modified a record
and Larry provides an update, then the entry will be duplicated and user
will have to resolve.

Also, this assumes a HotSync conduit for DB that can store in a file
format where it knows each record from the next.

Tom

Re: How do you update [Was: Re: [pilot-db-list] current 0.3.x status

[Hal D. <hal...@ea...>]

>>>>> On Wed, 12 Apr 2000, "Tom" == Tom Dyas wrote:

  Tom> Also, this assumes a HotSync conduit for DB that can store
  Tom> in a file format where it knows each record from the next.

Exactly so.

On reading Larry's request I think it may even imply some sort 
of "user hook" in the conduit that would allow a 
database-specific bit of code to make a decision about the 
record.

It wasn't clear from Larry's description if the "using them" 
done by the end users would affect the same records that the 
"master copy" would be delivering or not.  Presumably the 
datebook-type conduit logic could handle the cases where a 
single database record was updated or created on one platform.


--Hal