Adrien Foulon

Any chance to have this bug fixed before v1 as this is currently a major bug that makes dates unusable and the fix is not breaking and very low complexity?

I think it would be quite simple to just add a few method to relationships Like: ```js comment: this.hasMany(Comment, 'user_id').cascadeOnDelete() post: this.hasMany(Post, 'user_id').setNullOnDelete() Address: this.hasOne(Address, 'user_id').restrictOnDelete() ``` And then use...

Anything more than 1000 in JS is a very large dataset, and might not be appropriate for frontend use, I have some apps with lazy loading of data still using...

It all depends on how critical your data is and how you load it. You can insert it in intervaled chunks of 500, otherwise the CPU needed to process all...

Do you mean you're doing one insertOrUpdate of initial data with says 5000 rows and then another insertOrUpdate with those same 5000 rows? Then it makes sense that it's slow,...

I'd recommend doing ```js if (Object.prototype.toString.call(v) === '[object Date]') { v = isFinite(v) ? v : null; return v; } ``` To handle invalid dates and avoid issues from dates...

The getter seems the right approach to me, I would think of lazy loading as a way to have missing entities that when requested can be loaded from an API...

To answer my previous question it works completely fine Any update on the lazy loading feature? We have the relations on the instance so it'd be great to be able...

A commonjs should always be provided for a nodejs lib, there is 0 reason to bundle only esm because it makes it unusable for 90% of cases Please consider adding...

The Crawl errors are all gone as well from the API