Re: [Hibernate-devel] Question:

[Brad C. <bra...@wo...>]

gavin

probably not, but that is going to dependant on each rdbms.

as for ms sqlserver, a multi-column index is a candidate if the first column
of the index is used in the where clause.  is the key column the first
column in the index?

for operations that only select the key, an index only on the key column
would possibly be of more benefit.  the downside is you take a performance
hit on maintaining the extra index on inserts and updates.

brad

----- Original Message -----
From: <Gavin_King/Cirrus%CI...@ci...>
To: <hib...@li...>
Sent: Thursday, August 22, 2002 7:59 PM
Subject: [Hibernate-devel] Question:


>
> I've enhanced SchemaExport to create primary key constraints for indexed
> collections ( consisting of the key + index columns ). I'd like to know if
> its still worth creating an index on the key columns if there is a primary
> key on the key + index columns. Collection retrieval uses the key columns
> only.
>
> A bit beyond my understanding of databasey stuff i'm afraid....
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Hibernate-devel mailing list
> Hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>