continuational

35 ms·

481.
by continuational 11y ago
That's not how TM is supposed to work; it should not be possible for one atomic block to observe an uncommitted write of another atomic block. It must act as if each atomic block acquires a single global lock, executes, and then releas
482.
by continuational 11y ago
How can you be so sure that's the only other case?
483.
by continuational 11y ago
If we had selected from or joined on BOOK, it would be a Boolean expression. But in this case, BOOK is undefined, so BOOK.LANGUAGE.eq("DE") shouldn't type check at all. The corresponding SQL is nonsensical: select * fro
484.
by continuational 11y ago
> type safe SQL queries Really? So the compiler will catch this error? create.select().from(AUTHOR).where(BOOK.LANGUAGE.eq("DE")) No it won't, because `where` has this type: SelectConditionStep<R> wher
485.
by continuational 11y ago
While it certainly would be nice to outsource this problem, ph.hash("s3kr3tp4ssw0rd") ph.verify(hash, "s3kr3tp4ssw0rd") Is pretty damn easy.
486.
by continuational 11y ago
Feels like a nicely responsive and down-to-earth editor. It'd be great with a color scheme that emphasized your own variables and fields. It's not that helpful to draw attention to constants, keywords and arbitrary non-reserved id
487.
by continuational 11y ago
Wait, did you mean int16 z = (x + y) as int16; or int16 z = (x as int16) + (y as int16); ?
488.
by continuational 11y ago
Why is PostgreSQL considered to have a steep learning curve? At least coming from another SQL database, it's a 5 minute install and has none of the weird quirks like "the empty string is null" etc.