On Fri, October 3, 2008 12:33 pm, Stephen Russell wrote: > In reality, what are you getting in a refresh? > 1) any updates done while this data was brought local. > 2) secondary data refresh for inventory count >0 > 3) some other reason? > > >> From that reply you have to design how you want to handle the >> situation. > for #1 attempt your update as dynamic SQL to only update row(s) because > the same starting data exists for the overwrite against the dataset you > currently have.
That's why the timestamp field is great in some RDBMSes...that allows you to get the records that have been updated since the last time or avoid just slinging the same data back and forth. Surely don't commit changes to data you didn't change (like blind updates). > > So you build up the list of columns to apply your change(s) to and > then run it. If you get a count back >0 for rows changed great. Otherwise > someone beat you to an edit. Right > > For a #2 you have to just query that your count of existing ??? is > still available before you write the row. I don't follow you on that one. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
