home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Talk
Synchronizing client databases
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Anthony Vaughan" data-source="post: 1269372" data-attributes="member: 153283"><p>I have given you samples of code doing it both ways and why only a unique ID will work. My method avoids having to compare every record in the source table to see whether it exists in the target table. This matters when there are thousands of records. I have developed commercial systems involving tens of millions of records and this design allows data to be accessed and retrieved in less than a second. SQLite is not an enterprise database so addressing performance, and using every trick possible, is even more important.</p><p></p><p>I would be very happy to hear, in detail, how using a compound key could achieve what we my code does; i.e. only writing new data to the target table without having to read any records in the target table first.</p><p></p><p>Tony</p></blockquote><p></p>
[QUOTE="Anthony Vaughan, post: 1269372, member: 153283"] I have given you samples of code doing it both ways and why only a unique ID will work. My method avoids having to compare every record in the source table to see whether it exists in the target table. This matters when there are thousands of records. I have developed commercial systems involving tens of millions of records and this design allows data to be accessed and retrieved in less than a second. SQLite is not an enterprise database so addressing performance, and using every trick possible, is even more important. I would be very happy to hear, in detail, how using a compound key could achieve what we my code does; i.e. only writing new data to the target table without having to read any records in the target table first. Tony [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Synchronizing client databases
Contact us
RSS
Top
Bottom