-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Select of Person with wrong index-name #1253
Comments
Its not really pleasure to figure out things when you have |
But i have to use the generator, if i would not use the generator in my project, i would have to create over 30 Models by Hand. Thats not very convenient for me. But I have a Workaround for now: Using the QueryBuilder allows me to only select the values i really need and prevents the orm from selecting all values. Still waiting for a real solution approach |
Its still not clear for me what issue you have. |
I assume the issue is that the select is wrong done. ...
`person`.`mailBlogYnKeyTypKz` AS `person_mailBlogYnKeyTypKz`
... The attribute name is different here: @ManyToOne(type=>lov_jn_kz, mail_blog_yn=>mail_blog_yn.persons4)
@JoinColumn()
mail_blog_yn:lov_jn_kz; Dosnt make sense for me at all. |
okay, lets me ask you one thing, how your column is called in the database? If its called @ManyToOne(type=>lov_jn_kz, mail_blog_yn=>mail_blog_yn.persons4)
@JoinColumn({ name: "mail_blog_yn" })
mail_blog_yn:lov_jn_kz; And if that solves your issue then report issue in generator, because its generator issue. |
Yes, appearently its a issue of the generator. Thanks for the help, i will create an issue there. |
When i try to Select a Person with .find() it does a select as it should. But the Select has several fields in it i did not declare like like this. Example:
Field:
Info: The Entity was generated with TypeOrm-Model-Generator
The Select looks like this in the log:
Here the code and the Connection setup:
Here the Person.ts and the complete sql statement and some data about my table persons.
Select-Problem.zip
The text was updated successfully, but these errors were encountered: