v4.4.8, The "we don't talk about how it looked before" release

v4.4.8, The "we don't talk about how it looked before" release

This release is a full internal overhaul focused on code quality, type safety, and long-term maintainability. No new features — just the package finally having its life together.

What changed:

• Join renamed to FetchJoined, buildJoinPart → buildSqlJoinPart, things are now named after what they actually do, revolutionary concept
• Relation handling got alias support and smarter fallbacks for relation names, less silent mystery behavior
• QueryComparisonParameters now used consistently across all query builders, no more every builder doing its own weird thing
• Spatial distance parameters enhanced, InvalidWhereConditionError introduced, bad conditions now throw loudly instead of just silently producing garbage SQL
• Table.ts and Record.ts deprecation started, these two are on death row, begin your migration now
• JSON insertion fixed, objects and arrays are now properly serialized to JSON strings before hitting the database (yes, this was broken, no we don't talk about it. Also I have no idea if it really works but it should so hey :D)
• Exports switched to default across the board
• Unused model event types ripped out, dead code that was just vibing rent-free
• New test suite added: Model.test.ts, JsonInsertion.test.ts, Repository.test.ts, and more, the package now actually has tests, which is a choice we're choosing to make

pg-v4.0.9

###Bugfix
Nullable contraint in migrations didn't work before, now it should.

pg-v4.0.10

##Minor bugfix

core-v4.4.7

###Small bugfix

core-v4.4.6

Major bugfix where whereId didn't set the original attributes

core-v4.4.5

✨ Added: Nested Relation Support (Relation of Relation)

This update introduces support for nested relationship loading (relation of relation).

You can now eager-load relations through other relations using dot notation.

Example

    RecipeOutputs() {
        return this.hasMany(new RecipeOutput(), "recipe_id", "id");
    }

    OutputItems() {
        return this.hasMany(new Item(), "id", "item_id", "output_items.items", "output_items");
    }

The ORM will now correctly resolve and join:

Major
 └─ InternshipCompany (ManyToMany)
       └─ Address (hasOne)

What This Enables

• Eager loading of nested relations via dot notation
• Support for relation chains across junction tables
• Structured nested hydration of related models

Internal Improvements

• Nested relations are tracked and processed in join generation
• Improved relation graph traversal

core-v4.4.4

Full Changelog: core-v4.4.3...core-v4.4.4

core-v4.4.3

Fixes

• Fixed a bug where the base where conditions would disappear when you would join tables and not give a where condition on the join.

core-v4.4.2

Full Changelog: core-v4.4.1...core-v4.4.2

core-v4.4.1

Full Changelog: core-v4.4.0...core-v4.4.1