We like to be able to specify a collation for 1 specific column in a table in the model.
Currently our default database collation is set to SQL_Latin1_General_CP1_CI_AS
We have this special column that really wants be case-sensitive and wants to be unique preferably Latin1_General_100_CS_AI_SC_UTF8 so that not only case-sensitive uniqueness is guaranteed but als super/subscripting for cubic meters for example. The latter can be achieved, but we cannot seem to find a way to make this specific column case sensitive/sub/supercripting ‘aware’ towards the database.
We also would like to have the user interface to react to it as it was case insensitive in lookups for example. How can I achieve such functionality? An example is milliohm [mΩ] to meg(a)ohm [МΩ] (or mOhm and MOhm) - the column for such unit has to be unique since they actually really mean a load of difference in resistance, but I want them to be found by the user when typing in any case ‘mohm’ which currenly follows the collation rules:
above is Latin1_General_100_CS_AI_SC_UTF8 (needs UTF8 and case sensitive for for both case and sub/superscripting uniqueness) where you can see that the client will act accordingly to the collation - which we do not want to happen.
We want the user to have a result in a lookup that gives both options despite the collation settings:
We do not want to bypass the SF-model or fiddle around with tags or dynamic(ly)/manually generated stuff.
