		@@ -196,3 +196,3 @@ # Linked QL

		✨ _Now, that translates to: about 50% code, and whole namespacing exercise, having been eliminated! And yet: no questions asked about your schemas; no such thing as the usual upfront relationship mapping!_
		✨ _Now, that translates to about 50% code, and whole namespacing exercise, having been eliminated! And yet, no questions asked about your schemas; no such thing as the usual upfront relationship mapping!_

		@@ -207,3 +207,3 @@ Taking things further, multi-level relationships also get a corresponding pattern: multi-level paths:

		and for when you need to model the different forms of relationships out there (one-to-many, many-to-one, many-to-many), path operators that go in any direction:
		and for when you need to model the different forms of relationships out there (one-to-many, many-to-one, many-to-many), path operators can go in any direction:

		@@ -227,3 +227,3 @@ ```sql

		This means: game on with the regular JOINs for whatever calls for them; take the "magic path" option for whatever doesn't benefit otherwise!
		This means, game on with the regular JOINs for whatever calls for them; take the "magic path" option for whatever doesn't benefit otherwise!

		@@ -277,3 +277,3 @@ We think this will make a lot of the tooling and manual work around SQL obsolete and your codebase saner! And notice how this gives you back SQL - and every other thing as only an extension of that!
		```js
		// As an axample of what you will see:
		// As an axample of what you see:
		console.log(savepoint.description); // Create users table
		@@ -309,3 +309,3 @@ console.log(savepoint.versionTag); // 1

		✨ _Now, that translates to: all the engineering work you once did manaually now having been moved to the database! Plus, your schema histories now having been encoded as data (instead of as files), making them queryable, analyzable, and even visualizable, as regular data!_
		✨ _Now, that translates to all the engineering work you once did manaually having been moved to the database! Plus, your schema histories now having been encoded as data (instead of as files), making them queryable, analyzable, and even visualizable, as regular data!_

		@@ -312,0 +312,0 @@ Taking that further, you also get a way to roll forward from a rollback! (Much like hitting "Redo" to reverse a certain "Undo"). This time, you simply specify a "forward" movement from your current point in time:

@linked-db/linked-ql - npm Package Compare versions

Worsened metrics