Re: Partitioning
Hello Rick,
thank you for taking the time to respond to my query.
>>"For your example data, you are expecting 3 rows for 'MC001', correct?"
In this example, I provided it returns 3 row, but in reality it could return -- depending on how many records match -- anywhere between 100 to 1000 rows, based on URI value (i.e. MC001). The actual length of URI could be ~50 chars.
>>"Is `id` supposed to be unique? Is some other column (or combination of columns) expected to be unique?"
The ID will be unique and it will be an auto-increment.
>>"How big can URI be?"
Do you mean the length of it? If so, it can be ~50 chars.
If you mean how many records one URI can return, it can return upto around 1000 record. However, some may return very few.
So to clarify a little more, my SELECT, which the application will always do against this table, looks something like this:
SELECT START_CM, END_CM, SCORE FROM BOOK_TBL WHERE URI='MC001'
I haven't decided whether to make just ID as the primary key or include URI as part of PK, if it makes the SELECT query run faster?
Thank you.