Databases are such an essential building block of anything significant in I.T…
For the longest time, I have worked with relational databases such as MS SQL Server, Oracle and then #MySQL when it became usable (around v3.23).
MySQL later forked to MariaDB, which still has its place for data that requires referential integrity (it’s also well integrated into #homeassistant . However, for my own devs, I now prefer #clickhouse for log & time series data. I also like #SQLite for fast local-running databases.
MySQL offers pretty useful functions when you want to manipulate days: You can add a time interval to a date value with ADDDATE() or DATE_ADD() You can subtract a time interval from a date value witf DATE_SUB() You can find the interval between two…
mySQL has been planing to implement stored procedures and triggers in mySQL 5 for some time now... But lately, it looks like it's just gonna get better than expected... Via Simon Willison (great blog!), from chromatic's wrap-up of OSCON day 3: Brian…...
Think of the history of data access strategies to come out of Microsoft. ODBC, RDO, DAO, ADO, OLEDB, now ADO.NET - All New! Are these technological imperatives? The result of an incompetent design group that needs to reinvent data access every goddamn…
No referential integrity No transactions (at least not enabled by default so hosting providers would have them) No subqueries in DELETE statements No UNION statement (can you believe it?) and of course no triggers of any kind... Not that I think mySQL…...
Looks like mySQL is not able to to perform the DISTINCT selection in cases like this: SELECT DISTINCT YEAR(post_date), MONTH(post_date) FROM whatever1 INNER JOIN whatever2 ON field1 = field2 ORDER BY post_date This can be worked around, but it seems…