That looks awesome. Can't do it now but I'm trying it Monday
pohart
I love that differences with gnu are bugs. I know it will lead to slower, less maintainable code, but it makes adoption worlds easier
Any ides have support for this? I feel like I've been waiting forever.
I was there for it. It was a lot like mine, but more optimistic
What does the one liner do?
I once had to work with a government agency that insisted they generate and provide my private key.
Regardless of what pattern it is, you have a clear performance need and a testable implementation. That's a win.
Beyond looking for a pattern, I'd look at what your doing to make sure you're not loading a ton of extra dependencies of your know you won't use them.
Also, you generally want a database transacting to be one logical unit of work, that all commits or all rolls back together, if you're combining multiple transactions is likely what you want, but be aware that you might be holding locks for longer, so you might be introducing contention.
By the same token, make sure you've got records locked if you need them locked. If you had atomic updates before, or your first update locked the records you needed, you may need to lock records explicitly to keep your database consistent.
How much could performance even improve?
I wrote myself an app that was very useful to me personally. I knew zero others who might be interested but was able to publish it. At its peek there were 100 users. It was relevant for just under two years and is now gone. That was super successful and useful for the people who used it. I would have had no way to get it to anyone but me had this policy been in place.
Edit: I don't even know 20 Android users. Maybe 5. Everyone uses iPhones.
Definitely voting for someone who doesn't support genocide for president. Down ballot I'll likely vote 3rd party as well, but I haven't decided for sure.
We just point a backend developer at it and hope.