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: 1269367" data-attributes="member: 153283"><p>I meant that the Time_Stamp column is not unique.</p><p></p><p>I wasn't aware that the rowed table in SQLite is implicit. Thank you for pointing that out to me.</p><p></p><p>There is one issue about rowid that concerns me. Please look at this link <a href="https://www.sqlabs.com/blog/2010/12/sqlite-and-unique-rowid-something-you-really-need-to-know/" target="_blank">rowid</a>. I think this demonstrates why an explicit INTEGER PRIMARY KEY is a better solution because I absolutely need to guarantee that the integer key does not change for file comparisons across databases to work (I need the integer key field to have the same key value for each row in each version of the each database).</p><p></p><p>Tony</p></blockquote><p></p>
[QUOTE="Anthony Vaughan, post: 1269367, member: 153283"] I meant that the Time_Stamp column is not unique. I wasn't aware that the rowed table in SQLite is implicit. Thank you for pointing that out to me. There is one issue about rowid that concerns me. Please look at this link [URL='https://www.sqlabs.com/blog/2010/12/sqlite-and-unique-rowid-something-you-really-need-to-know/']rowid[/URL]. I think this demonstrates why an explicit INTEGER PRIMARY KEY is a better solution because I absolutely need to guarantee that the integer key does not change for file comparisons across databases to work (I need the integer key field to have the same key value for each row in each version of the each database). Tony [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Synchronizing client databases
Contact us
RSS
Top
Bottom
