Thanks for looking into this, Alex. You’re right there are other issues I’ve encountered (example, you can’t have an insert statement with getDate() in it, which is something Flyway does when logging a schema migration). So the plan is to look into having a logical separation between the cdm datasource and our ohdsi results. We could possibly support the option where our cdm datasource is in a highly optimized for read structure (hadoop? Polybase? Some other non relational form) where we do the analysis and then the the results datasource is used to persist analytic results, or define research studies, or other basic research activities that require application support tables. Frank started the discussion over here:
I don’t have any plans to change anything in the WebAPI; I’m going to try to work on a way of integrating with it from an app specifically geared towards dealing with APS envornments. But I’m hoping some of the lessons learned there will drive some enhancements in the OHDSI stack.
-Chris