Currently, when exporting a table to an Aurelius class, any database fields that aren't flagged as not-null are created as Nullable in the class. When working with legacy databases where many fields are not-null, but don't need to be, this extra layer adds nothing of need and actually results in more complicated code in the application (having to check for null fields).
Right now, I use search and replace to change all of the Nullable, etc. entries to native types - integer in this case. An override checkbox in the export screen which would force all exports to native types would save a lot of work