Currently, generateSqlSchema will generate SQL to create a schema based on the results data model specification which may include constraints (primary keys at the moment). In the case that we are bulk-loading results from a study, we may want to add constraints after data is loaded.
I'd propose we extend generateSqlSchema to allow for a new parameter includeConstraints = TRUE so we can optionally disable constraints. The add another function generateSqlContraints to generate the SQL necessary to apply any/all constraints.