Re: Partitioning
Posted by: Ahmad Sakhi
Date: April 21, 2016 07:47AM

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.

Options: ReplyQuote


Subject
Written By
Posted
April 19, 2016 12:29PM
April 20, 2016 11:34PM
Re: Partitioning
April 21, 2016 07:47AM
April 22, 2016 06:41PM
April 22, 2016 06:59PM
April 23, 2016 05:11PM
April 25, 2016 09:27AM
April 30, 2016 05:08PM
May 04, 2016 11:41PM
May 09, 2016 09:18AM
May 10, 2016 10:15AM
May 11, 2016 08:11AM
May 17, 2016 07:49AM
May 23, 2016 03:21PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.