3 ms·
IIRC spark can optimize it away, and in OO there shouldn't be user_id
by cztomsik 6y ago
IIRC spark can optimize it away, and in OO there shouldn't be user_id
- airstrike 6y ago> in OO there shouldn't be user_id I don't think that's right. There is a user_id column in the book table, so why shouldn't there be book.user_id?
- cztomsik 6y agodepends if you're doing active record (which I am not considering as typical ORM) or data mapper like hibernate where your entity is POJO with id and annotations but typically no foreign keys (just references to other model classes) hibernate is then "the magic "environment where it just works" I realize OO is out of fashion now but it's still true and it still works and I've been in a lots of projects where ORM was useful