I have a large Team Center 3.2 customization running on Oracle (I know, it is old stuff). I would like to make the query by attributes case insensitive for some attributes. In the 'API Model Reference Guide' the term insensitive is listed as a MODeL keyword, but I can find no other reference to it. Any help would be most appreciated.
Thank You,
Toby Patton
"A frequent problem with communication is the assumption it has been achieved" - source unknown
Thanks for the response. Unfortunately, those calls are not available in my version (3.2)
Since our Oracle database is running on a massive Sun box I am thinking about adding a hidden attribute to the object that I will populate with the data from the actual attribute after forcing it to lower case. Then I will override the AllowQueryBuildOfAttr method to use the alternate attribute and the lower case version of the query value. There are only two attributes that I need this functionality for, so it shouldn't be an expensive query.
Thank You,
Toby Patton
"A frequent problem with communication is the assumption it has been achieved" - source unknown
Hi Toby,
Good lack,
--
You received this message because you are subscribed to the Google Groups "Teamcenter Enterprise Customization" group.
To post to this group, send email to teamcenter-enterp...@googlegroups.com.
To unsubscribe from this group, send email to teamcenter-enterprise-c...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/teamcenter-enterprise-customization?hl=en.
Kevin
Thanks for the suggestion. My problem is that the text has to remain in the case it was typed in. There are two string(2000) variables that need to retain their case, but have case insensitive query capabilities. Since my version of Team Center does not support case insensitive queries using standard API calls I decided to try something. I am already over-riding DoCreatePre, DoUpdatePre and DoCopyPre on my custom class for other reasons, so I just added some code to take what the user typed in and convert it to lower case then store it in an attribute that is on the object, but not the dialog. I then override AllowQueryBuildOfAttr to capture the construction of the SqlPtr for the two attributes and use oiSqlWhereLikeEQ on the hidden and lower case attribute. I did use Oracle SqlPlus to populate the existing items. There are only about 200,000 of these objects, so there is no noticeable performance hit. Initial testing seems positive.