This column exists in the Sat schema but not hosted. This inconsistency makes it difficult to write code that will work with both codebases. This column should behave the same as the login_uc column.
Plan is to actually remove the email_uc from wupi in satellite. The required functionality will be acoomplished by the upper(email) index.
Column removed from satellite schema.
Column *not* removed from satellite schema. However, the index has been added in hosted. Not sure what's going on with this.
any reason we can't get the column removed from the sat schema? We still would like it removed so we can simplify the java code.
Well, we went with the index on upper(email) in hosted b/c it was too impractical to add a column for email_uc (and populate it) on hosted. However, to use the index we had to use a hint in the query. The only issue with hints is that they force the use of Oracle's cost based optimizer (CBO) as opposed to the rule based optimizer (RBO). RHN typically tries to stick with the rule optimizer. No big deal for hosted really, b/c we can keep on this query in hosted and if the CBO starts doing something funky we can mediate those. For a satellite though, I don't know if we want the embedded db switching between CBO and RBO. We would have to see if there were any issues. So, I don't know if it's worth the work just to have the Java code simplified, although it may be. Might be a good idea to get other folks thoughts on CBO vs. RBO in a satellite. Sorry for the brain dump, I had to get my thoughts straight on what we had already done.
User jslagle's account has been closed