[Kupietz]Yeah, seen it many times... even in my work, people don't have a choice because I'm building bespoke databases that run their business... but users will put up with an annoyance or bug for months and not say anything because "we don't want to bother you" :facepalm:
cotsuka, grufwub and [KevinMarks] joined the channel
[KevinMarks]Or they start reusing fields because they don't want to bother you to add a new one and now you have a field that can mean 3 differnt things
NegateThis joined the channel; NegateThis left the channel
[Kupietz]Believe it or not, I haven't seen that one on the user side. I've seen developers do things like that, though. "Let's see... emails are from a sales rep, to a client, so let's make Emails a child table of Sales Reps, and also of Clients. Oh, and Invoices also have a sales rep and a client, so let's keep emails and invoices in the same table."
[capjamesg][snarfed] Iām measuring the time it takes to run the query in Python with the `sqlite` package on the back-end.
srazkvt, barnaby, oodani, ax562, NegateThis, [artlung], [pcarrier], Elleo, jeremycherfas, lain` and [schmarty] joined the channel; NegateThis left the channel
[Kupietz]Yeah, I'm actually on 8.4 now on my main sites. I did actually see one breaking change on a client site moving from 8.2 to 8.3 last year, there was some deprecated syntax that finally became a breaking change, but that's the only issue I've seen.
[Kupietz]Frustratingly I didn't log the exact issue I saw. It was something with using braces or brackets in a way that had previously been supported and now wasn't.