Perl 6 - the future is here, just unevenly distributed

IRC log for #metacpan, 2016-09-13

| Channels | #metacpan index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:50 rsrchboy joined #metacpan
05:35 oiami joined #metacpan
07:20 neilb joined #metacpan
07:54 ranguard [Tux]: I saw :(
07:54 ranguard but I have a plan for logging :)
08:13 neilb joined #metacpan
08:14 Tux ranguard, http://tux.nl/Files/20160913101401.png
08:16 Relequestual joined #metacpan
08:55 edward joined #metacpan
08:58 osfabibisi joined #metacpan
09:01 ranguard Tux: right, so that's our backend taking too long to process the request
10:38 anon joined #metacpan
11:06 Tempesta joined #metacpan
13:12 karjala (perlmodules.net) I think I need to modify the way releases are sorted in my RSS feeds. Right now they're sorted by chronological order, so if module 1.3 & 1.5 already exist and 1.4 is saved just now, then 1.4's RSS body will contain the diff between 1.5 and 1.4, instead of 1.3 and 1.4
13:12 karjala I think that's wrong, and releases should be ordered by version number
13:22 karjala Would using the decimal version number provided by the API (like 1.005008 instead of 1.5.8) work well for such sorting?
13:23 karjala And how many decimal digits should I store in the database? I see for example Net-FullAuto-0.99999999999951 and Net-FullAuto-0.99999999999952 would require lots of digits to properly differentiate between themselves.
13:28 karjala hmm, it seems that the decimal versions don't seem to work correctly. For example:
13:29 karjala ClearPress-v471.0.0 and ClearPress-v471.0.3 both have decimal version = 471.0000000000
13:30 karjala do we have a standardized way to compare version numbers like v471.0.0 and v471.0.3 ?
13:30 karjala How does MetaCPAN sort the releases it has?
13:31 karjala on its website, I mean
13:32 fontardion joined #metacpan
13:37 fontardion joined #metacpan
13:40 haarg karjala: the decimal version should work
13:40 haarg how are you seeing 471.0 for v471.0.3?
13:40 rpaz joined #metacpan
13:45 karjala haarg: i saved 471.0 directly from the API. Let me call the API once again.
13:45 karjala and tell you
13:55 karjala haarg you are actually right, version_numified is 471.000003
13:55 karjala How many decimal digits max are needed?
13:58 karjala I mean how many digits should I store in the database to be safe and avoid collisions? How many digits max does version_numified have?
14:00 jberger karjala: which database are you using? can you just use a TEXT field?
14:00 jberger I guess if you want to be able to act on it numerically you need a mathy type
14:01 karjala mysql 5.6. i use the database field type of DECIMAL(20,10)
14:01 karjala I'll do it with text, and then maybe I should try to do comparissons with Math::BigRat??
14:02 karjala the point is that I wanted MySQL to do the sorting (indexed, like "bring me the latest 15 release versions")
14:02 karjala DECIMAL(20,10) means 10 digits after the point, and 10 before
14:03 karjala on Ubuntu 64-bit 14.04
14:05 haarg karjala: max allowed length by pause is 16 characters
14:05 Relequestual joined #metacpan
14:05 karjala thanks, so 16 digits before and 16 digits after the point should be enough.
14:06 haarg possibly
14:07 haarg it may allow v1.1.1.1.1.1.1.1, which would expand to a very long decimal
14:31 MiinieMe joined #metacpan
15:13 Grinnz sounds like a job for an acme module
17:13 neilb joined #metacpan
19:03 fontardion joined #metacpan
19:46 y1mmm joined #metacpan

| Channels | #metacpan index | Today | | Search | Google Search | Plain-Text | summary