News for hackers. Stuff that matters.

vtman2002

Re:Ask HN: Who is hiring? (December 2016) on Thursday December 01, 2016 @04:31PM (#13083720)
Harvest Exchange | {Senior,Mid-level,Junior} Developer | Houston, TX | ONSITE, INTERNS

Fintech startup (hvst.com); funded. Python+Bottle+React framework. No-nonsense self-directed work environment.

Re:JOOQ: an alternative approach to traditional ORMs on Wednesday January 13, 2016 @08:57PM (#10899146)
that is shady. bit it looks like they're still there in the git history: https://github.com/jOOQ/jOOQ/tree/fc7afb40760246153da4a2334c...

even the stuff that has been xxxed out: https://github.com/jOOQ/jOOQ/blob/63717b517fccf475089648ca3c... and it's still under the APL.

Re:JOOQ: an alternative approach to traditional ORMs on Monday January 11, 2016 @02:36PM (#10882721)
Our pooling was pretty shitty actually, but it didn't need to be fancy as 95% of our code was some sort of batch processing (as you guessed), after which the JVM terminated. But yes, highly tweaked JDBC drivers over all.

Hibernate has iterator methods, but I recall (in 2010) it still loaded the entire result set into memory, with a //TODO comment. I remember thinking "W...T...F..." I can't tell you how many -Xmx16G (or 32/64) flags I deleted...

Re:JOOQ: an alternative approach to traditional ORMs on Monday January 11, 2016 @12:29PM (#10881769)
Correct, iterator-based-streaming, as java6 was the norm when I wrote this. And yes, you're obviously at the mercy of your JDBC driver. Though I'd argue if your results are fitting into PostgreSQL's default preload size (whatever it may be) you don't really need to worry about it. But I promise you it does stream. (TS is not known for it's small datasets...)
Re:JOOQ: an alternative approach to traditional ORMs on Monday January 11, 2016 @12:14PM (#10881673)
Fair enough. I don't know enough about jOOq to claim equivalency to your baby. I just wrote DKO to scratch an itch. (That itch being Hibernate!) Fully supportive of the general pattern, and glad you're free now for open source databases. In hindsight, perhaps I should have sought out VC funding. :)
Re:JOOQ: an alternative approach to traditional ORMs on Monday January 11, 2016 @11:43AM (#10881477)
Massive and continual support? That has not been my experience. Even after leaving TS, it looks like Lynch (who took over internal support: https://github.com/salynch/DKO) has make only a dozen or so commits. SQL is not a fast-changing target.
Re:JOOQ: an alternative approach to traditional ORMs on Monday January 11, 2016 @11:15AM (#10881269)
> Isn't the database simply a mechanism for persisting records/objects whose structure is determined by domain modeling?

not at all. you're thinking of a file system.

Re:JOOQ: an alternative approach to traditional ORMs on Monday January 11, 2016 @11:06AM (#10881212)
A fully open source equivalent: https://github.com/keredson/DKO

I wrote this for Two Sigma's internal use back in 2010.

Stop migrating your Ruby code

We've hit the 6-month mark of using db:evolve in production here at https://www.hvst.com. This was highly controversial at the time ("wait, you want to NOT use ruby migrations for schema changes? are you insane?!?"), but it turned out to be a huge time-saver. Even the devs who thought I was bat-sh!t crazy at the time now love it.Anyway, switching to (or back from) db:evolve takes seconds. ...

( Read More... | no comments | on HN )
Re:Java LINQ – C# LINQ examples running on Android on Saturday August 01, 2015 @01:08PM (#9987754)
this has a nicer syntax IMHO: https://github.com/keredson/DKO