Posted in Database Management Systems, Still-coding, Technology, tagged ai, ChatGPT, Database, Gemini, JSON Schema, programming, SQL on January 11, 2025| Leave a Comment »
In a previous post I showed how an AI system (ChatGPT) was an easy way of converting an SQL Schema to a JSON-Schema. It was very successful and could save hours of donkey-work when dealing with a legacy database. I am coding in TypeScript so I asked for a TypeScript schema as well. It also did that perfectly.
I asked Gemini to do the same job.
(more…)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 Database Management Systems, History, tagged CODASYL, Database, History, IT Pioneers, SQL on September 19, 2023| Leave a Comment »
If you are asked to name the most important pioneer in database development, the name Edgar Codd is probably the first name that comes to mind. He pioneered the concept of relational database. But another person deserves credit as well. Nearly a decade earlier Charles Bachman did fundamental work, developing the first database management system.
(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…)Posted in Still-coding, Technology, tagged CouchDB, Database, NOSQL on November 10, 2022| Leave a Comment »
Posted in Still-coding, Technology, tagged Database, Firestore, NOSQL on October 11, 2022| Leave a Comment »
I decided to use my lockdown project SUDSJS.com to test out a few different NOSQL database management systems (DBMS).
SUDSJS is written in JavaScript using the node.js server-side system and I designed it so that I could plug in different drivers for different databases. I wrote database drivers for MySQL, SQLite 3 and PostgreSQL. The first NOSQL system I tried was MongoDB, and the SUDSJS.com test site is currently running using this (correction – it is now running on CouchDB). The second NOSQL system I tried was Firestore from Google.
It didn’t go well.
(more…)Posted in Still-coding, Technology, tagged Database, MongoDB, NOSQL, SQL, sudsjs on September 29, 2022| Leave a Comment »
For the last 50 years there has been one and only one way of designing a database. SQL Database management systems (DBMS) have been the uncontested standard. (A better name is ‘relational’ because SQL is just the name of the language used to access them, but we will stick with it.)
But things have changed in the last 10-15 years. Databases that disobey relational rules are coming into vogue. The term NOSQL is used for these non-relational databases (the above chart is work in progress, but I have been looking at these systems.)
What is the difference between classic databases and this new breed?
Bob Browning's blog 