> Then I guess the current version of SQLite port won't leave enclave during > execution (since I make it support in-memory database only and it currently > does not introduce any additional ocalls)?
Yes. Your workaround is to give some non-functional stubs. This will still cause runtime errors. The best way is to trim those functions and APIs, and providing a customized SQLite only for SGX environment. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave-sgx-sdk/pull/274#issuecomment-716175842
