Pawel Pabian comments

Results 24 comments of


                                            Pawel Pabian

MySQL driver cannot handle bigint unsigned in `execute( )`

The issue refers to biggest MySQL numeric type that MySQL can handle. IMO this `else` part is not test-coverable (or is it?) and simple `if >0 then use uint64 else...

MySQL driver cannot handle bigint unsigned in `execute( )`

OK, then the fastest way seems to be (also with corrected range edges): ``` if -2**63

MySQL driver cannot handle bigint unsigned in `execute( )`

BTW: My project does round trip when writing data here: https://github.com/bbkr/UpRooted/blob/master/t/42-writer-mysql.rakutest#L28 So it is currently tested "up to int signed". I think your solution alone will work just fine, however...

MySQL driver cannot handle bigint unsigned in `execute( )`

Weird, on logical level this fix should be correct (Blobs do not overflow). Haven't looked in the test itself yet (I'm still in my $dayjob).

MySQL driver cannot handle bigint unsigned in `execute( )`

You're correct - it does not: https://dev.mysql.com/doc/c-api/8.0/en/c-api-prepared-statement-type-codes.html

MySQL driver cannot handle bigint unsigned in `execute( )`

So my fix proposal were based on wrong assumption, sorry about that. Looks like your version is the valid way to solve it and there will always be string casting...

Feature request : add prefered font size to settings...

Oh, I was looking for font size settings as well and there are **two** settings panels. WhatsApp internal settings in tripple-dot menu and application settings if you right click on...

Some tests still try to use the network even when NETWORK_TESTING is not set

This breaks CI for other modules using HTTP::UserAgent: https://travis-ci.org/bbkr/jsonrpc/jobs/351673499 .

`IO::Path::succ()` not working when IO::Path backtracks.

From IRC: timo m: say "/foo/bar/hi01.bla/test01.txt".IO.succ # it just uses the first dot it finds in the whole path, which is not what the docs say it should do camelia...

"You have to pass an explicitly typed..." message missing for typed Hash.

Also hint for message is weirdly formatted, may be worth fixing too.