Yurii Rashkovskii comments

Results 214 comments of


                                            Yurii Rashkovskii

Implement access to column meta information in query results

I honestly don't remember anymore :) But I'm happy to change this to `usize` tomorrow, or if it is the only thing blocking this one, feel free to change it...

Implement access to column meta information in query results

I've updated the PR to use `usize`

Implement access to column meta information in query results

I just did it consistently with the rest of SPI interface. Should those interface be updated eventually, too? On Fri., Oct. 21, 2022, 12:34 p.m. Eric Ridge, ***@***.***> wrote: >...

Any reason why PostgresType couldn't be an enum?

What I am after here is being able to derive `PostgresType` on enum to represent it as a regular (non-enum) type. I have a workaround at the moment that wraps...

[Crash] if tx queue has reached to parity node

What is the most preferable course of action in this case? (Considering that we don't have a persistent queue)

[Crash] if tx queue has reached to parity node

Should we designate a special exit for for this error so that the supervisor pauses before a restart?

[Crash] if tx queue has reached to parity node

Or would this better be served by persisting the queue of transactions?

Problem: time resolution on Windows is failing HLC guarantees

It looks like this is the right function to use: https://msdn.microsoft.com/en-us/library/windows/desktop/hh706895(v=vs.85).aspx It's part of winapi crate: https://github.com/retep998/winapi-rs/blob/e00f7f514950cf6906070793dd4dcb9f48c48e6e/lib/kernel32/src/lib.rs#L1306

Problem: time resolution on Windows is failing HLC guarantees

Good point indeed. Just not perfectly, and not consistently with Linux/OSX.

Problem: is overwriting key/value with the same value a duplicate?

The use case motivating the question is simplifying some code where it'll be easier not to handle this error and avoid checking if the exact pair is already present.