Debug Trace analysis

[giantkiller]

I post this to further the information on this feature.

My execution platform is an Oculus Go monitoring through ADM monitor on Win 10 Professional.

How does one find the trace file and to see the trace?

[echo17]

I am not familiar with the Oculus Go, but the debug trace for SimpleSQL is just written to the default console. It should be the same location that any other debug statements get written to for that device.

This search might help you find the answer: link

[giantkiller]

I have a db that I am assuming transfers with the APK over adb.

I can see log posts in Android Device monitor through the adb connection back at the pc.

I get failures on the

List<Pricedata> priceList = dbManager.Query<Pricedata>(sql);

I am under an NDA so I can not reveal too much of the project internals but I will try to be a specific as possible.

I then take the stance of creating a smaller test bed to try to find where the error actually is. This will in turn enable me to create more error handling or application correction logic to keep the user experience clean.

So then I created a new project with just the DB and the access code.

This new project resides on the pc and has no Oculus or android platform packages or includes.

This attempt runs fine. But...

The log showed 8 thousand records being accessed and displayed.

I deleted all the records but two and the pc side project keeps showing 8 thousand records.

I believe all files are in the their correct folders.

I use sqliteadmin to view the records in the correct places. I only see 2 records but the small project still shows 8000.

Has this got to do with the working file and the static file?

At this moment the log does not help. Probably because I am missing something.

What needs to be done to guarantee a system synchronization with the DB?

And then when I get this figured out and working I build to the Oculus and see where the next possible error might be.

[giantkiller]

Overwrite if exists! This corrected the problem.

I just started with this product so I have to become familiar with the options and nuances.

[echo17]

Thanks for the follow up. The DB in your project is an embedded resource and cannot be written to. For that reason, SimpleSQL copies the embedded db to a working directory on your device so that it can be updated at runtime. If you make changes to the project db, you will need to make sure the Overwrite if Exists is checked to get those changes propagated to the device. Be careful with this setting, however, as it will also wipe out your data that has been modified during runtime.

If you need to update structure without harming the data, you can create an upgrade path. Please see this FAQ for more information: link

[giantkiller]

What I found was a lazy attempt on my part for pulling the table data using:

select * from table

Data field mapping in Simplesql can not occur even though the visual studio shows naming conventions are good.