It seems rather rare that you will have an application with such a compound pk, and you will never want to ask for all rows that have C=x. But since it was marked as a todo and it was easy, I added an attribute skipHeavyIndexing that you can use on the table or database tags to shut it off on a table by table basis, or for the entire schema.
john mcnally josef richberg wrote: > > How can that lead to improved performance? I am > always providing all three keys so I will always use > the Primary Key index. How do the other two indexes > help? They take up space and need to be maintained, > so I see that as a hinderance. > > --josef > --- John McNally <[EMAIL PROTECTED]> wrote: > > josef richberg wrote: > > > > > ... > > > > > > If I designate 3 fields a "primary" (A,B,C), > > torque > > > will generate the following indexes: > > > > > > primary(A,B,C) > > > index(B,C) > > > index(C) > > > > > > That is incorrect. I would eventually like to > > change > > > it, but I'm starting small. > > > > > > --josef > > > > Why do you consider this incorrect? It will lead to > > improved > > performance, at least for mysql. > > > > john mcnally > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > __________________________________________________ > Do You Yahoo!? > Check out Yahoo! Shopping and Yahoo! Auctions for all of > your unique holiday gifts! Buy at http://shopping.yahoo.com > or bid at http://auctions.yahoo.com > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
