[DevExpress Support Team: CLONED FROM T569076: How I found out using Oids in clustered index in XAF is a very bad idea]
> One the most reliable ways would be ensuring that the default classes from the DevExpress.Persistent.BaseImpl library are not added
> into the list of exported types of your application. To do this, you can take the source code of these classes and implement your own
> versions in your project + configure the AuditTrailModule.AuditDataItemPersistentType property accordingly.
This is exactly what I did (see image attached) and when I am in Application Designer I can see my classes only, but for some reasons, somewhere original classes still end up in the app and clash with my own classes (unless I use different table names in which case both original and my tables are created).
As for default, you should probably introduce default attribute, something like DbTypeDefault("expression") so default expressions would be divided from db type because current system does not allow configuring primary keys with default value because all foreign key will be defined with the same value. Separate default attribute could solve this issue.