tag:blogger.com,1999:blog-7997313029981170997.post636524638611988511..comments2009-04-29T08:51:45.544-04:00Comments on End Point Blog: Inside PostgreSQL - Data Types and Operator Classe...Jon Jensenhttp://www.blogger.com/profile/18273388885281263476noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7997313029981170997.post-9471075238830884372009-04-29T08:51:00.000-04:002009-04-29T08:51:00.000-04:00To be honest, I don't know. What you're getting at...To be honest, I don't know. What you're getting at, as I read it, is if PostgreSQL will find an operator class that doesn't have all its strategies assigned, and synthesize operators for a particular strategy based on logical operations with the other operators. My guess is that no, it won't, but you could certainly roll your own operators based on operators you already have, and use those new ones to fill in gaps in the operator class.Joshua Tolleyhttp://www.blogger.com/profile/08481531515300677240noreply@blogger.comtag:blogger.com,1999:blog-7997313029981170997.post-87499175549961206162009-04-29T00:31:00.000-04:002009-04-29T00:31:00.000-04:00Can you synthesize equals and greater than from le...Can you synthesize equals and greater than from less than? ie:<br />(a = b) -> (not a<b and not b<a)<br />and<br />(a > b) -> (b < a)<br /><br />Sure having a faster == that doesn't have to do two comparisons may be faster in some situations, but greater than can very easily be ignored by just swapping the arguments if it's not present.Perry Loriernoreply@blogger.com