Purpose of crsql_wdbreplicator

[AlexErrant]

I'm trying to build a RESTish client/server layer. I'm basing it heavily off of the WholeDbReplicator. Is the entire purpose of crsql_wdbreplicator to alert remote nodes that a change has occurred in the local sqlite? The reason I ask is because I want to delete (from my code) installTriggers. If the answer to my question is "yes", I would feel safe deleting installTriggers since live updates aren't important in my app's planned database sync lifecycle.

[tantaman]

Is the entire purpose of crsql_wdbreplicator to alert remote nodes that a change has occurred in the local sqlite?

Yep, that's right. Completely safe to delete installTriggers if you don't need to be alerted to changes in the database

You might also be interested in the client-server sync reference implementation I've been working on
https://vlcn.io/docs/replicators as another example of a sync implementation.

The main difference with these is that they take more of a "streaming approach" rather than the simple "poke" approach.

[AlexErrant]

Wow, I didn't know that Sqlite could call external code via triggers, and upon failure roll back a transaction. That's powerful as heck.

[tantaman]

In the latest version I’m switching from triggers to the “update_hook”
which is called post rather than pre commit.

[tantaman]

cr-sqlite/js/rx-tbl/src/tblrx.ts

Lines 31 to 37 in 8f835a8

	this.db.onUpdate((updateType, dbName, tblName, rowid) => {
	// Ignoring updates to internal tables.
	if (tblName.indexOf("__crsql") !== -1) {
	return;
	}
	this.#preNotify(tblName);
	});

[AlexErrant]

Ah yeah, a post-commit hook makes more sense for notification/reactivity semantics.