Verify option { field: ["*"] }

[dungkaka]

I have entities City and School, that are OneToMany relationship.

@Entity()
class City  {
    @OneToMany(() => School, (s) => s.city, { ref: true })
    schools = new Collection<School>(this, undefined, false);
}

@Entity()
class School {
    @ManyToOne(() => City, { ref: true })
    city: Ref<City>;
}


const city = await this.em.find(City, { id: 1 }, { fields: ["*"] });
// Seem city will populate all relationships when fields: ["*"]
// Expected result: city without populate anything
// Real result: city will populate all relationships

It causes maybe due to new feature of populate: ["*"] on v6. I just want to verify it then I can refactor my code. Thank you so much!

MikroORM: 6.0.4
NodeJs: 20

[B4nan]

Why do you set fields: ['*'] in the first place? What you want is the default behavior, just drop that (or provide fields: undefined instead).

[dungkaka]

I use it v5, for example, in case when I want to just select a field from school:

const city = await this.em.find(City, { id: 1 }, { populate: ["schools"], fields: ["*", "schools.name"] });

Assume that my entity city have many relationship, and I have a query that populate schools and only some fields of school, example "name". Because field: " * " now will populate all things, I can not using " * " anymore, so now I need explicit declare all field of city in fields:

const city = await this.em.find(City, { id: 1 }, { populate: ["schools"], fields: ["id", "name", "createdAt", "updateAt", "many other fields", "schools.name"] });

Yeah, if it change behavior in v6, I will refactor my code.

[B4nan]

Isn't this working the way you want already?

const city = await this.em.find(City, { id: 1 }, { populate: ["schools"], fields: ["schools.name"] });

Either way, I don't mind fixing this, should be pretty simple, just trying to find a workaround till it gets fixed.

[B4nan]

Hmm actually, the problem you are describing can only be present if you skip the populate hint, it won't be an issue in the code you provided in this thread, where you set populate: ['school']. There is no inference if you provide it.

[dungkaka]

Aha, you're right. It's my mistake in my example. Actually, I often use fields: ["*"] for retrieve lazy scalar property instead of using populate, what why I get many errors because of auto populate on my project when upgrading now. Sorry for my unclear example !

[dungkaka]

Isn't this working the way you want already?

const city = await this.em.find(City, { id: 1 }, { populate: ["schools"], fields: ["schools.name"] });

Either way, I don't mind fixing this, should be pretty simple, just trying to find a workaround till it gets fixed.

Can you make this syntax also available with em.populate. For example:

const city = await this.em.find(City, { id: 1 } });
await this.em.populate(city, ["schools"], { fields: ["schools.name"])
// If I use this now, it will ignore all other fields of City, 
// I can solve it by { fields: ["*", "schools.name"] }

But I'm like this syntax instead of { fields: ["", "schools.name"] } which I use before, because [""] will also get lazy property.

[B4nan]

It is already fixed in latest version.

[dungkaka]

Do you mean v6.0.5? Thank you for fixing many unwanted behaviors I meet on this release.
I've updated to v6.0.5. In this case, I'm not sure because  it's still need ["*", "schools.name"] instead of ["schools.name"].
If you're mentioning v6.0.5, I'll check more.

[B4nan]

Only if you started providing complete reproductions... It's hard to navigate in this stream of short and incomplete snippets.

[B4nan]

It sounds like you reported two problems (this and #5138) and now the last missing step is the combination of those.

[B4nan]

Here is a fix for the em.populate with partial loading, let's hope it won't break anything, it was quite tricky to find the way to handle this.

1c7b446