Ich habe gerade mit „Erschrecken“ festgestellt, wie lange ich schon PhpStorm nicht mehr geöffnet habe. Das war eine Update-Orgie, die einem Windows alle Ehre gemacht hätte. Und dabei wollte ich nur schnell mal einen Blick auf den Datenbank-Client werfen. Weil ich sowas in der Art jetzt auch direkt in neovim habe: https://www.insomniaonline.de/ein-datenbank-client-in-neovim#neovim#database
The world of big data, databases, and R is rapidly evolving with an explosion of tools and packages. We're delighted to announce two workshops at posit::conf(2024) tailored for working with large datasets:
• Big Data in R with Arrow, led by Nic Crane and Steph Hazlitt
• Databases with R led by @kirill
#TodayInHistory 1984 - Ashton-Tate introduces the dBase III relational #database program for IBM PC-compatible computers.
dBase was one of the first database management systems for microcomputers and the most successful in its day. The dBase system included the core database engine, a query system, a forms engine, and a #programming language that tied all of these components together.
This is the first time I work for a company that I actively want to personally advertise for, but I really like what #Grist does. It's like a #spreadsheet that's really a #database and lets you use #Python as a computational language. And it's all open source!
I just had to explain to our "technical" "Product Owner"
The difference between a Database Server and Database.
Now maybe im being to picky here. but shouldn't someone in charge of a product that is built around databases understand the basic functionality of Database Servers?
Just published a minor update (version 5.1.1) to JavaScript Database (JSDB) that optimises the custom data type¹ serialisation code by removing a redundant return statement:
This change is backwards compatible and shouldn’t require and updates to your projects, including the ones you have in Kitten (which uses JSDB internally).
• Forgetting to pass a custom class that’s persisted in your database in your JSDB.open() call now throws instead of corrupting your database by falling back to using an untyped object.
• Added JSDF ver. 2 to 3 database migration script (i.e., JSDB version 2-4 to 5)²
100% test coverage doesn’t mean your code’s bug free but it did just lead me to find and fix an issue in JavaScript Database (JSDB)¹ with a code path that wasn’t being hit that I would have otherwise missed because it was causing the relevant test to pass.
¹ JSDB is a zero-dependency, transparent, in-memory, streaming write-on-update JavaScript database for the Small Web that persists to a JavaScript transaction log (an append-only log).
To really drive home the above 👆 point that 100% test coverage does not mean ‘bug free’, just found a bug in JSDB¹ 5.0.0 where running JSON.stringify() on a complex custom object (actually: the automatic Proxy of the custom object created by JSDB) results in an error.
Already have a failing test and about to implement fix.
(It’s at this point where the test harness is invaluable.)