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
Development
General Development (no feature request here!)
Database: Refactor MP1 database for multi seat usage
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: 1287897" data-attributes="member: 153283"><p>Exactly. And it is now much faster as a consequence of designing the database to make optimal use the database engine. This is how relational databases are supposed to work - not with fields containing iterations of string data; not to mention joining tables using string columns rather than numbers. The size issue isn't irrelevant though. Index size is critical to optimal performance. When you have string primary keys you force indexes to be far larger than indexes over number fields. All relational database engines are designed to access numeric indexes far more quickly than string indexes. This is really basic stuff.</p><p></p><p>I am not trying persuade anyone to do anything they don't want. I am only offering an alternative that provides multi-user capability and optimal database design and performance. I gain nothing either way and I will support what I develop if I am asked to. </p><p></p><p>I now have a system that has run error free for weeks. It's a win-win for me and an easy life from now on if no-one else is interested. I will help if asked.</p><p></p><p>Tony</p></blockquote><p></p>
[QUOTE="Anthony Vaughan, post: 1287897, member: 153283"] Exactly. And it is now much faster as a consequence of designing the database to make optimal use the database engine. This is how relational databases are supposed to work - not with fields containing iterations of string data; not to mention joining tables using string columns rather than numbers. The size issue isn't irrelevant though. Index size is critical to optimal performance. When you have string primary keys you force indexes to be far larger than indexes over number fields. All relational database engines are designed to access numeric indexes far more quickly than string indexes. This is really basic stuff. I am not trying persuade anyone to do anything they don't want. I am only offering an alternative that provides multi-user capability and optimal database design and performance. I gain nothing either way and I will support what I develop if I am asked to. I now have a system that has run error free for weeks. It's a win-win for me and an easy life from now on if no-one else is interested. I will help if asked. Tony [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Database: Refactor MP1 database for multi seat usage
Contact us
RSS
Top
Bottom