Nitrite Database
-
|
You lastest builds destroyes db files, it's HUGE bug. Find cause, I can not help you, coz I've tested your builds for 5 days and you've not foubd out what's wrong. Your library is UNSTABLE! |
Beta Was this translation helpful? Give feedback.
Replies: 0 comments 14 replies
-
|
Tone down dude!! You didn't answer properly in the last question in the other discussion if the error is happening with build number 333 along with jackson 2.12.0. And also I told you there was no code changes, so it should be some dependency that is creating problem in your project. You only need to help me out by finding which one is creating problem for you, I am not going to debug your code. Moreover, I am not obliged to any SLA to fix any issue in a snapshot build. If you want stability you can take any stable build that is available. You need to understand that this is not my full time job. I'll only spend time here whenever I have some time from my day job. |
Beta Was this translation helpful? Give feedback.
-
|
May be latest mvstore does not support android 7, you can try changing the mvstore version in your dependency. Rocksdb is NOT for android. You can try mapdb adapter, but performance is not good like mvstore as per jmh - https://github.com/nitrite/nitrite-jmh |
Beta Was this translation helpful? Give feedback.
-
|
Performance loss is about 20%? |
Beta Was this translation helpful? Give feedback.
-
|
Sometimes more. You can try and see what is it in your case. |
Beta Was this translation helpful? Give feedback.
-
|
I tested your code from master on 7.1.1 and I have not seen any error what you are describing. I tested it on standard x86 emulator image of Android 7.1.1.
And I see it is generating 16 mb around db file and I rerun the application several times and I could not see any error regarding nitrite. In the logs there are other errors, I have attached the logs also here. I am thinking the error you are getting must be tied with the custom ROM you are using and I can't help you there as I don't have such devices. |
Beta Was this translation helpful? Give feedback.
-
|
That issues, I was faced, appears suddenly. There is no system, it works for a couple of days stable and than BOOM! MVStore issue tracker shows same issues from other devs, I've added link previously. And devs of MVStore close all this issues as 'difficult to reproduce'. In fact your library is hostage of MVStore in Android projects. You cannot guarantee any stability because of this external issue. Exceptions in log are connected to emulator, so it's normal |
Beta Was this translation helpful? Give feedback.
Tone down dude!! You didn't answer properly in the last question in the other discussion if the error is happening with build number 333 along with jackson 2.12.0. And also I told you there was no code changes, so it should be some dependency that is creating problem in your project. You only need to help me out by finding which one is creating problem for you, I am not going to debug your code.
Moreover, I am not obliged to any SLA to fix any issue in a snapshot build. If you want stability you can take any stable build that is available. You need to understand that this is not my full time job. I'll only spend time here whenever I have some time from my day job.