Description
This is more a marker issue to improve the platform independence of Torque. In the OM templates I found that the only point left where platform-dependent code is generated is MapBuilder.vm There, tMap.setPrimaryKeyMethodInfo() is set depending on the selected database platform. If that could be removed/changed, the generated classes would be free of platform dependent code which in turn would allow to switch between database backends without re-generating the OM-classes.