Tim Jones

Another and probably better solution is now available for Android 7+ API 24+ , follow the recommended solution here https://developer.android.com/training/articles/security-config which also means that the solution is not just specific to SymmetricDS initiated HTTPS calls. One significant issue with the previous solution above is that by setting https.allow.self.signed.certs the socket factory is set globally for all HTTPS connections, this prevents for example Google Maps working as mentioned here...

Hi, I am upgrading from 3.8.to 3.13 and have run into a couple of run time issues. 1) One of the AbstractSqlTemplate.queryForCursor() methods was modified in rev 0005053 (13/7/2021) and is now recursive (is also flagged by my IDE) without any break condition see https://github.com/JumpMind/symmetric-ds/blob/3.13/symmetric-db/src/main/java/org/jumpmind/db/sql/AbstractSqlTemplate.java as opposed to the earlier version https://github.com/JumpMind/symmetric-ds/blob/3.11/symmetric-db/src/main/java/org/jumpmind/db/sql/AbstractSqlTemplate.java....

I have some experience with both IndexedDB and the Android/Java SymDS client. Some things you might want to consider is if you intend modelling the data as relational with foreign keys in Postgres you will need to ensure the correct ordering from the NoSQL IndexedDB client and how you will demark the batches within transactions. IndexedDB (at least when I used it) has no triggers so you will need to capture the changes in your own framework. I definitely agree with Eric that at some stage you should...

I have some experience with both IndexedDB and the Android/Java SymDS client. Some things you might want to consider is if you intend modelling the data as relational with foreign keys in Postgres you will need to ensure the correct ordering from the NoSQL IndexedDB client. IndexedDB (at least when I used it) has no triggers so you will need to capture the changes in your own framework. I definitely agree with Eric that at some stage you should look at the SymDS code base, particularly the client(s),...

I have some experience with both IndexedDB and the Android/Java SymDS client. Some things you might want to consider is if you intend modelling you data as relational SQL with foreign keys in Postgres you will need to ensure the correct ordering from the NoSQL IndexedDB client. IndexedDB (at least when I used it) has no triggers so you will need to capture the changes in your own framework. I definitely agree with Eric that at some stage you should look at the SymDS code base, particularly the client(s),...

Hi Gregg, I am not an authority on SQLite and have really only dealt with it in terms of Android but I think it has the same multi write limitation whether running on Android or not in that only one process can write at a time (see https://www.sqlite.org/wal.html "However, since there is only one WAL file, there can only be one writer at a time.") so I don't think it is a very good candidate for a central node. I am assuming you are runing in WAL mode. Tim

Hi Gregg, I am not an authority on SQLite and have really only dealt with it in terms of Android but I think it has the same multi write limitation whether running on Android or not in that only one process can write at a time (see https://www.sqlite.org/wal.html "However, since there is only one WAL file, there can only be one writer at a time.") so I don't think it is a very good candidate for a central node. Tim

Hi Timo, I am not a committer on this project but yes the Android clients store their changes and resync when communication with the server is restablished.