aanari

Joined 14 years ago

Karma

Submissions

Member since

Mar 14

My name is Ali. I am an expert in data science, and I run a small data science consultancy named Datom Solutions. I create a competitive advantage for venture-funded startups and financial service companies by combining domain knowledge with specialist technical skills to deliver high-impact statistical insights, predictive models and data-driven business advice.

I am based in Los Angeles, but completely available to work with clients in San Francisco because I'm happy to travel, super communicative, and always available by Skype, email, phone, and FaceTime.

Email: [email protected]

Website: https://datomsolutions.com

LinkedIn: https://linkedin.com/in/alianari

View on Hacker News

Recent submissions

Comment · 3 years ago

Awesome work!

Comment · 7 years ago

Nice work VGS team!

Comment · 7 years ago

I am extremely interested!

Comment · 8 years ago

Nootropics can help with this too esp. as you get older -

www.getmindsync.com

DM me if you would like to try some for free.

Comment · 9 years ago

Awesome Cieplak, best of luck to you and the team @ Finix!

Comment · 11 years ago

Great concept + execution! Can't wait to see the export functionality and for it to start gaining momentum in the market :)

Comment · 11 years ago

That's correct, as jpitz mentioned if the code is run inside a transaction block, then we don't have to worry about the failing DELETE causing the INSERTs to fail.

Comment · 11 years ago

Author here. That's a great point bhahn, I just updated my gist to properly handle the case that you just outlined:

https://gist.github.com/aanari/349c7d97ed50c6f69930#file-bat...

By creating a separate function for the locking and updating of rows, we ensure that the `BEGIN/END` transaction is handled per iteration rather than at the very end, so we only lock rows while they are being processed. Since Postgres does not support nested transaction blocks, calling a defined function from within an anonymous function block seemed to be the easiest and clearest path to achieve this.

Comment · 11 years ago

No problem mizerable! Glad you enjoyed it.

Comment · 11 years ago

That's a good clarification. I think it's better for the data migration to error out when acquiring the lock on rows and then retry, rather than waiting indefinitely, but YMMV (your mileage may vary).

Comment · 11 years ago

Author here. Great point, I just updated this link to point directly to his comment rather than his HN profile.

Comment · 12 years ago

That's a great point tantalor, thanks for sharing.

Comment · 12 years ago

Hello, author here,

I recommend App::pmuninstall for this task:

pm-uninstall [options] Module

https://metacpan.org/pod/pm-uninstall