it's not as if the rest of the world is using one standard.
2015-05-15 13545, 2015
jesus2099
but both DD-MM-YYYY and YYYY-MM-DD are logic
2015-05-15 13514, 2015
derwin
if we're looking for a country to make fun of.. Canada?
2015-05-15 13531, 2015
derwin
Social Insurance applications for Canada use DMY format. / Passport applications[35] and tax returns[36] use YYYY MM DD. / Immigration Canada Stamps use DD/MM/YYYY and Canada Customs Stamps use MMM/DD/YYYY.
2015-05-15 13532, 2015
jesus2099
grey means… it depends ?
2015-05-15 13543, 2015
jesus2099
« ça dépend, ça dépasse » (another private joke, sorry)
can I prepopulate the fields in the edition creation form via get or post?
2015-05-15 13531, 2015
shmias
in bookbrainz I mean
2015-05-15 13549, 2015
shmias
the fields don't even have names yet
2015-05-15 13504, 2015
mb-chat-logger
New post: blog: Schema upgrade downtime: Monday, 18 May, 2015 @ 17:00 UTC <http://blog.musicbrainz.org/2015/05/15/schema-upgrade-downtime-monday-18-may-2015-1700-utc/>
2015-05-15 13529, 2015
Freso
jesus2099: Smaller table row ids *are* older than bigger ones — but sometimes older entities get merged into newer ones, thus the older data gets "moved" to a newer table row id.
2015-05-15 13544, 2015
Freso
Oh, you said as much yourself.
2015-05-15 13547, 2015
Freso
Never mind me then.
2015-05-15 13520, 2015
pankkake
derwin: I suppose MMM is the Month in letters. So it's OK, it's always M between D and Y or unambiguous text
2015-05-15 13540, 2015
Freso
If shmias comes back, they should probably be redirected to #bookbrainz or #bookbrainz-devel
2015-05-15 13546, 2015
shmias joined the channel
2015-05-15 13555, 2015
yeeeargh joined the channel
2015-05-15 13522, 2015
Zastai joined the channel
2015-05-15 13536, 2015
Zastai
hmm, the "Lookup CD" page lists matching media, but for this disc at least, it has "Medium" under Format despite the format being set properly on the release (to "CDV"). known bug?
2015-05-15 13538, 2015
jesus2099 joined the channel
2015-05-15 13542, 2015
JoeLlama joined the channel
2015-05-15 13556, 2015
jesus2099
Freso: so each time an old recording A is merged into a newer one B, the result is an old edit history with the newer MBID as primary and row ID of B (greater than A’s ID) or a new one (that is then even greater).
2015-05-15 13504, 2015
Eggs_ joined the channel
2015-05-15 13540, 2015
jesus2099
So it means it’s exactly what I want it to be in my comparisons, row ID is the age of an MBID (not the age of an entity, which is found in its edit history), that’s great. :)
2015-05-15 13550, 2015
jesus2099
I will remove my slow detect (search of the first entity edit ever) as it is then misleading when we want the age of the primary MBID. Thank you for your own explanation, Freso, it is helpful.
2015-05-15 13536, 2015
jesus2099
(indeed I found a release merge in that older entity with more recent ID, that explains)
2015-05-15 13537, 2015
Zastai
jumping in here without seeing the entire convo: unless this is an application-managed rowid, that's probably not a safe assumption. especially when records are deleted, it would be possible for a new record to be stored in the gap left behind, and depending on the database, that could correspond to a lower rowid
2015-05-15 13540, 2015
darthanubis joined the channel
2015-05-15 13516, 2015
jesus2099
sure but it seems ID are always growing
2015-05-15 13539, 2015
jesus2099
and I know it’s very weak hint but it’s all I got as to estimate MBID age. :)
2015-05-15 13532, 2015
jesus2099
but yes, I also had this worry before switching to this fast detect of oldest MBID (row ID)
2015-05-15 13534, 2015
Zastai
would be good to introduce created/changed timestamps perhaps - but it would then probably be hard to initialize them correctly
2015-05-15 13554, 2015
jesus2099
but more or less it’s only useful to a handful of OCD
2015-05-15 13506, 2015
jesus2099
merging into a newer MBID is not that dramatic :)
2015-05-15 13521, 2015
Zastai
db is postgres right now, isn't it? could be that it guarantees sequential rowids, which makes the point moot anyway
2015-05-15 13546, 2015
Zastai
not used postgres; mainly db2/oracle/mssql/mysql
2015-05-15 13515, 2015
jesus2099
if row id ever disappear from MB or become unreachable in <html>, then my code will rot and that’s all. :)
2015-05-15 13555, 2015
Zastai
btw, now that I have you here jesus: are there any plans to integrate your ISRC submission script into MB pages (like mass merge is)?
2015-05-15 13534, 2015
jesus2099
it would be better and it wouldn’t have to wait for some caching/something delay after new release addition indeed…
2015-05-15 13538, 2015
jesus2099
i have been wanting this for myself for months and months but i don’t have time to make it… i/you should create a github issue maybe… not that it would kick me doing it faster
