[dev] MSSQL portability options

[Matt Selsky]

> I would make it per db, like we already do it in Kronolith. BTW, that  
> reminds that we had the same problem with Oracle where we used CHAR  
> fields instead of VARCHAR. CHAR fields were always padded to the full  
> length. Do we leave Oracle alone because it can be fixed by using the  
> correct column types, or do we want to RTRIM them too, to be on the  
> safe side?

Let's use the correct column types for Oracle and leave it be.  We 
already created an upgrade script for Oracle to help admins fix the 
column type.


-- 
Matt