> On Dec 9, 2019, at 7:43 AM, George wrote:
>
> (litesync - SQLite Replication and Synchronization)
> litesync seems to be a version of sqlite made by Ramos Bernardo from Brazil.
Interesting, but I don't see how they can make those kinds of claims without
running into conflicts on primary
thank you Jens,I have just found litesync
(litesync - SQLite Replication and Synchronization)
litesync seems to be a version of sqlite made by Ramos Bernardo from Brazil.
|
|
| |
litesync - SQLite Replication and Synchronization
litesync makes easy to replicate and synchronize SQLite
> On Dec 5, 2019, at 8:05 AM, George wrote:
>
> Changes -> bidirectional. All terminals can save to db. Amount of collected
> data it's not big and frequency between readings will be minimum 2sec. When
> we push more readings. Data itself it's very small. Like reading temperature
> from a
On 5 Dec 2019, at 4:48pm, George wrote:
> We have an app already done in Qt on all terminals. Sqlite it's already used
> by this app.
When a terminal makes up a SQL INSERT command to add new data to the database,
have it also save this command to a file. That's the file you send to the
On Thu, 2019-12-05 at 12:54 +, George wrote:
> [EXTERNAL SOURCE]
>
>
>
> Hi,
> I need to sync sqlite tables over network between few devices.
> Please help me with an opinion with what will be the best approach ?
> thanks,
> George
> ___
>
We have an app already done in Qt on all terminals. Sqlite it's already used by
this app. The only missing part it's our sync to have data on PC for reports
and also on screen reports on terminals if operator will need to check.We need
sqlite because help us to manage data on terminal and
Okay. Do you really need all of the terminals to have up-to-date data from all
the terminals ?
If not, it's a simple problem: each terminal sends data to the master, which
puts all the incoming data into the same database. Terminals don't need a SQL
dataase at all. They simply report
Hi Simon,
I miss to talk about sync trigger. Will be great to be after post trigger. I
mean we read a probe on terminal T1, save data and on post trigger also put a
job for sync and leave it on other thread to do this. If some sync jobs fail
will must to try again to sync or on timeout stay in
Hi Simon,
Thx for helping me. I'm trying to explain our setup next:
Changes -> bidirectional. All terminals can save to db. Amount of collected
data it's not big and frequency between readings will be minimum 2sec. When we
push more readings. Data itself it's very small. Like reading
On 5 Dec 2019, at 12:54pm, George wrote:
> I need to sync sqlite tables over network between few devices.
> Please help me with an opinion with what will be the best approach ?
Unfortunately this is a subject which has no simple solution. The things you
have to do are not simple. To help us
Hi,
I need to sync sqlite tables over network between few devices.
Please help me with an opinion with what will be the best approach ?
thanks,
George
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
11 matches
Mail list logo
