News for hackers. Stuff that matters.

A comment on To ORM or Not to ORM. Parent comment

Re:To ORM or Not to ORM by pjmlp on Wednesday May 08, 2019 @01:47AM (#19856171)
Around 10 years ago, a work collegue improved the ETL processing time of a Java application from minutes to a couple of seconds, by dropping hibernate and using direct JDBC instead.

If all one is doing is calling createNativeQuery() all the time, and having stored procedures as well, then it is just needless fat.

[ Parent | on HN ]
Re:To ORM or Not to ORM by stickfigure on Wednesday May 08, 2019 @02:42AM (#19856420)
If you have a trivial app that just executes a couple queries, then sure use JDBC?

I do not understand your point. Most business apps are not trivial.

[ Parent | on HN ]
Re:To ORM or Not to ORM by pjmlp on Wednesday May 08, 2019 @05:06AM (#19857101)
Who said anything about it being a trivial app?

It was an ETL stack for distributed networking monitoring, and data reporting.

[ Parent | on HN ]
Re:To ORM or Not to ORM by stickfigure on Wednesday May 08, 2019 @10:38AM (#19859201)
If you can comfortably use JDBC for data access, then your data access logic isn't very complicated. There's nothing wrong with that; use the right tool for the job.
[ Parent | on HN ]
Re:To ORM or Not to ORM by alexnewman on Thursday May 09, 2019 @10:19AM (#19868496)
I believe the exact opposite
[ Parent | on HN ]
Re:To ORM or Not to ORM by pjmlp on Wednesday May 08, 2019 @11:18AM (#19859615)
Who said it wasn't complicated?

Using SQL with JDBC isn't a synonym for bare bones string concatenation.

Offload complex queries to external files, or better yet, stored procedures.

[ Parent | on HN ]