mORMot Open Source

h.hasenack

Member

From: Nijmegen, Netherlands

Registered: 2012-08-01

Posts: 173

Website

Trouble using in-memory tables with latest .obj fils (and pmy own .obj

Tracing into this stack:

Mormot_D17.mORMotSQLite3.TSQLVirtualTableModuleSQLite3.SetDB($FE7BE000)
Mormot_D17.mORMotSQLite3.TSQLVirtualTableModuleServerDB.Create(TSQLVirtualTableExternal,$FE6213C0)
Mormot_D17.mORMotSQLite3.TSQLRestServerDB.InitializeEngine
Mormot_D17.mORMotSQLite3.TSQLRestServerDB.Create($FE7CEEE0,$FE7BE000,True)
Mormot_D17.mORMotSQLite3.TSQLRestClientDB.Create($FE7CD560,$FE7CEEE0,$FE7BE000,TSQLRestServerDB,True)
Mormot_D17.mORMotSQLite3.TSQLRestClientDB.Create($FE7CD560,nil,':memory:',TSQLRestServerDB,True,'')
SGMormotTestSuitePkg_D17.uTestMormotDBBaseCommon.TMormotDBBaseCommonTest.SetUp
SGMormotTestSuitePkg_D17.uTestMormotDBBaseCommon.TMormotDBBaseCommonCRUDTest.SetUp

fails to initialize for the 2nd table initialized, being the AuthGroup table.
When tracing into the "sqlite3_check" routine, it reveals the return code is 21, and an exception is raised with a _very_ informative text: "not an error"

I have no idea how to proceed from here. Tips are very welcome.

regards - Hans

h.hasenack

Member

From: Nijmegen, Netherlands

Registered: 2012-08-01

Posts: 173

Website

Re: Trouble using in-memory tables with latest .obj fils (and pmy own .obj

Never mind. It turned out to be my own mistake: I had added the AuthGroup and AuthUser tables to the model, and also provided Trie for handleautorhization=True to the TSQLRestClientDB.Create()

Sorry - Hans