Support case sensitive columns

Hi,

Both SqlServer and MySQL supports the ability to set the collation on a column (as the following SQL Server example)

CREATE TABLE [dbo].[AuthenticationToken] (
    [AuthenticationTokenId]    INT            IDENTITY (1, 1) NOT NULL,
    [UserId]                   INT            NOT NULL,
    [OpenIdClaimedIdentifier]  NVARCHAR (250) COLLATE SQL_Latin1_General_CP1_CS_AS NOT NULL,
    [OpenIdFriendlyIdentifier] NVARCHAR (250) NULL,
    [CreatedOn]                DATETIME       NOT NULL,
    [LastUsed]                 DATETIME       NOT NULL,
    [UsageCount]               INT            NOT NULL
);

It is critical for security to force a this whether or not the underlying database is configured to be case insensitive. Any chance migrations can support this as an additional parameter? Take into account that I use UTF8 and MySQL (in my current project) and others mat use different charsets.

It seems there are some commonality between the collations of MySQL and SQL Server. Perhaps a enum would suffice with LightSpeed translating it to the correct SQL when performing a migration. Or it could just be an boolean to be case sensitive and another for unicode and LightSpeed can pick the correct field type and collation.

Thanks, Werner

PS This may also be very useful for supporting UNICODE when the defaults of the database isn't configured by default to support UNICODE. This way we can force the table or column to support UNICODE.