Posted in Database Management Systems, Still-coding, tagged Database, json, JSON Schema, programming, SQL, sql-server on January 9, 2025| Leave a Comment »
I have been working on my hobby project, which is a generic database updating tool. It uses an extension of the JSON-Schema standard. But how do you deal with a new database from a legacy database.
I found a really simple solution, I asked ChatGTP to produce a JSON-Schema based on a database dump – which happily is a set of SQL statements.
(more…)Posted in History, Technology, tagged json, XML on July 8, 2023| Leave a Comment »
For decades, software developers had to struggle with getting computers to talk to each other. Businesses developed systems to do different things at different times on different hardware, and integrating the data was rarely on peoples priority lists. Customers would tell the bank about changing their address and still get mail about their mortgage sent to an old address because the mortgage system had it’s own address file.
Then came XML. A standardised way of exchanging information, with formal standards for different types of application. For example: FIXML – Financial Information Exchange and BEERXML – Brewing information. There is a list here. There are about a thousand of them.
XML is human-readable and similar to well-know HTML so easy to use if a little long-winded.
Well, I am glad that is done and dusted. A major problem for IT systems has been solved. Then came another standard.
(more…)Posted in Database Management Systems, Still-coding, Technology, tagged Database, express, json, node.js, NOSQL, sailsjs, schema, SQL on May 4, 2023| Leave a Comment »
A schema means different things for an SQL and a NOSQL database management system. If you are using SQL, you have to tell the system about the format of the data before you can use – that is the schema. When it comes to NOSQL databases everything is different. You don’t need a schema, you simply present data and the system stores it in whatever format you send it.
Each document in a collection1 can be a different layout and different types of data. The flexibility of NOSQL databases suggests that data design is less important. For example I read: “… since NoSQL doesn’t necessitate the need for a schema, you avoid the expense and time of that initial design stage.”
I don’t think so
(more…)
Bob Browning's blog 