Yeah the keys would be part of the first condition of the where clause...

this table is like this:
username | siteid | bannerid | clicks | someotherstat


an update would be like: update tbl set clicks=clicks+1 where
username='something' and siteid='something' and bannerid='something'

a select would be: select clicks from tbl where username='something' and
siteid='something' and bannerid='something'


so knowing this, does it make sense to make primary keys out of
username,siteid,bannerid?

Thanks!

- Noah


""Manuel Lemos"" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Hello Noah,
>
> On 23-Jun-01 12:10:20, you wrote:
>
> >I see,
>
> >What about if you had 3 or 4 columns that would always be unique, is
there
> >an advantage to naming them as primary keys? does this slow inserts
because
> >it has to check if theres a duplicate entry?
>
> What really slows down is updating the index with the new entry value.
>
> Anyway, some times it may pay to slow down inserts and updates for very
> large tables.  You have to check if the indexes/primary keys that you are
> adding are used as the first condition of the WHERE clause.
>
>
>
> Regards,
> Manuel Lemos
>
> Web Programming Components using PHP Classes.
> Look at: http://phpclasses.UpperDesign.com/?[EMAIL PROTECTED]
> --
> E-mail: [EMAIL PROTECTED]
> URL: http://www.mlemos.e-na.net/
> PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp
> --
>
>
> --
> PHP Database Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
>



-- 
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to