Primary key value not detected with alias'ed Column about typeorm HOT 8 CLOSED

Great, I did not realize you already refactored a lot. It does not hurry with the new version.
And we can do some "testing" when we are evaluating typeorm for our project where we have a lot of custom column names.

from typeorm.

Here is another bug:
https://github.com/typeorm/typeorm/blob/master/src/persistment/PersistOperationExecutor.ts#L488
propertyName should be name in L488 and L493 as key for conditions.

from typeorm.

fixed in 1b4295b

from typeorm.

0.0.2-alpha.63 is released, there are some breaking changes, mostly in the connection options, take a look on connection options interface in the docs

from typeorm.

Looks like I already did this in master. I was planning to release a new version next week, it contains lot of new features and breaking changes. Are you okay to wait? (if you are not I can release urgently)

I hope there are not too many other cases where an alias breaks the whole application.

I hope too. Custom column names isn't well tested feature, no one test or sample using it. So I don't recommend to use it yet, but if you need it, then become a first tester and will fix all issues quickly together :)

from typeorm.

When are you planning this next release now?

from typeorm.

there are few things left, and I planned to release it on Monday - Thursday. But I can do release right now, if you need it

from typeorm.

Yes that would be great

from typeorm.